<?xml version="1.0" encoding="ISO-8859-1"?>
	<rss version="2.0">
		<channel>
		<lastBuildDate>Wed, 22 May 2013 22:26:01 -0500</lastBuildDate>
		<title>Garage4hackers</title>
		<description>Recent Content from Garage4hackers</description>
		<link>http://www.garage4hackers.com</link>
			<item>
				<pubDate>Tue, 14 May 2013 22:02:00 -0500</pubDate>
				<title>Change OAuth Target URL &amp; Domain Description [ UI redress attack ]</title> 
				<description>To Change OAuth Target URL &amp;amp; Domain Description Can be achieved using Clickjacking Vulnerability . &lt;br /&gt;
&lt;br /&gt;
Status: Fixed&lt;br /&gt;
&lt;br /&gt;
OAuth is cool and simple to understand developer can integrate with Google 's OAuth endpoints seamlessly and effortlessly . Google Provider a Panel to manage the Return URL &amp;amp; Domain Description by using following URL.&lt;br /&gt;
&lt;br /&gt;
Vulnerable URL : &lt;div class=&quot;bbcode_container&quot;&gt;
	&lt;div class=&quot;bbcode_description&quot;&gt;Code:&lt;/div&gt;
	&lt;pre class=&quot;bbcode_code&quot;style=&quot;height:36px;&quot;&gt;https://accounts.google.com/ManageDomain?authsub_msd=anydomain.com&lt;/pre&gt;
&lt;/div&gt;On the page there two input</description>
				<link>http://www.garage4hackers.com/content/152-change-oauth-target-url-domain-description-ui-redress-attack.html</link>
				<guid>http://www.garage4hackers.com/content/152-change-oauth-target-url-domain-description-ui-redress-attack.html</guid>
			</item>
		
			<item>
				<pubDate>Wed, 13 Mar 2013 05:27:00 -0500</pubDate>
				<title>File Uploading Issue in BillMeLater.com- paypal worth $5000</title> 
				<description>I want to share my finding on a recent issue I found in a subdomain of BillMeLater.com (a Paypal service).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On 1st March, during my regular course of bug hunting in Paypal services, I found a file uploading issue that allowed me to upload files of certain extensions on the BillMeLater server.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Initially I noticed the website was running an outdated version of &lt;b&gt;DotNetNuke&lt;/b&gt; (an ASP.NET based CMS) with the file uploader enabled. Allowed extensions were:&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;*. docx, *.xlsx, *.pptx, *.swf, *.jpg, *.jpeg, *.jpe, *.gif, *.bmp, *.png, *.doc, *.xls, *.ppt, *.pdf, *.txt, *.xml, *.xsl, *.css, *.zip, *.spin &lt;/b&gt;&lt;br /&gt;</description>
				<link>http://www.garage4hackers.com/content/150-file-uploading-issue-billmelater-com-paypal-worth-5000.html</link>
				<guid>http://www.garage4hackers.com/content/150-file-uploading-issue-billmelater-com-paypal-worth-5000.html</guid>
			</item>
		
			<item>
				<pubDate>Tue, 12 Mar 2013 05:50:00 -0500</pubDate>
				<title>Paypal Zong Service Credit card  &amp; Billing Info Update CSRF</title> 
				<description>&lt;b&gt;Vendor product Brief Information &lt;/b&gt;:  Zong aim Frictionless Mobile Payments to the world. Zong processing millions of payments a month in over 40 countries worldwide.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;CSRF Vulnerable URL &lt;/b&gt;: &lt;a href=&quot;https://my.zong.com/ZPlusConsumerConsole/linkCC/creditCardLink&quot; target=&quot;_blank&quot;&gt;https://my.zong.com/ZPlusConsumerCon...creditCardLink&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
CSRF is an attack which forces an end user to execute unwanted actions on a web application in which he/she is currently authenticated(OWASP).&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;POC&lt;/b&gt;:&lt;br /&gt;
&lt;br /&gt;
&lt;div class=&quot;bbcode_container&quot;&gt;
	&lt;div class=&quot;bbcode_description&quot;&gt;Code:&lt;/div&gt;</description>
				<link>http://www.garage4hackers.com/content/149-paypal-zong-service-credit-card-billing-info-update-csrf.html</link>
				<guid>http://www.garage4hackers.com/content/149-paypal-zong-service-credit-card-billing-info-update-csrf.html</guid>
			</item>
		
			<item>
				<pubDate>Fri, 08 Mar 2013 01:45:00 -0600</pubDate>
				<title>DEP ASLR bypass without ROP JIT : CanSecWest2013 Slides and Analysis</title> 
				<description>I have my own talk from CanSecwest to blog about but this one is more interesting and the most awaited one. So here are the slides, I will add my own analysis and test cases to this blog entry later. Interesting thing is we had this technique discussed on garage in november &lt;a href=&quot;http://www.garage4hackers.com/f22/win7-64bit-no-aslr-dep-bypass-required-vinnu-3080.html&quot; target=&quot;_blank&quot;&gt;http://www.garage4hackers.com/f22/wi...innu-3080.html&lt;/a&gt; .&lt;br /&gt;
&lt;br /&gt;
Yu Yang @tombkeeper did a demo of his technique on Ms013-08 and it does not ever need a heap spray for his ASLR/DEP bypass technique .&lt;br /&gt;
&lt;br /&gt;
And the exploit is scary, its a quick kaboom with out heap spray.&lt;br /&gt;
He calls his method GIFT</description>
				<link>http://www.garage4hackers.com/content/148-dep-aslr-bypass-without-rop-jit-cansecwest2013-slides-analysis.html</link>
				<guid>http://www.garage4hackers.com/content/148-dep-aslr-bypass-without-rop-jit-cansecwest2013-slides-analysis.html</guid>
			</item>
		
			<item>
				<pubDate>Fri, 22 Feb 2013 05:57:00 -0600</pubDate>
				<title>Facebook Mobile Open Redirection Vulnerability</title> 
				<description>Sometime back, I found an open redirect vulnerability in Facebook mobile site (&lt;a href=&quot;http://m.facebook.com&quot; target=&quot;_blank&quot;&gt;http://m.facebook.com&lt;/a&gt;)&lt;br /&gt;
&lt;br /&gt;
According to OWASP:&lt;br /&gt;
&lt;br /&gt;
&lt;div class=&quot;bbcode_container&quot;&gt;
	&lt;div class=&quot;bbcode_quote&quot;&gt;
		&lt;div class=&quot;quote_container&quot;&gt;
			&lt;div class=&quot;bbcode_quote_container&quot;&gt;&lt;/div&gt;
			
				An open redirect is an application that takes a parameter and redirects a user to the parameter value without any validation. This vulnerability is used in phishing attacks to get users to visit malicious sites without realizing it
			
		&lt;/div&gt;</description>
				<link>http://www.garage4hackers.com/content/147-facebook-mobile-open-redirection-vulnerability.html</link>
				<guid>http://www.garage4hackers.com/content/147-facebook-mobile-open-redirection-vulnerability.html</guid>
			</item>
		
			<item>
				<pubDate>Mon, 04 Feb 2013 03:06:00 -0600</pubDate>
				<title>Fuzzing DTMF Detection Algorithms .</title> 
				<description>My ekoparty.org [Argentina] and NU[Delhi] talk and also Ruxcon [Australia] and BlackHat [Abhudabi] which I could't make it . &lt;br /&gt;
&lt;a href=&quot;http://www.garage4hackers.com/content/attachments/589-mqdefault.jpg.html?quot;=  title=&quot;Name:  
Views: 
Size:  &quot;&gt;Attachment 589&lt;/a&gt; &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;What is this paper about&lt;b&gt;&lt;/b&gt;:&lt;br /&gt;
&lt;/b&gt;&lt;br /&gt;
Input validation attacks and memory corruption attacks are common, and the &lt;br /&gt;
criticality of finding a DOS attack on a service like HTTP is consider a lot critical &lt;br /&gt;
considering the attack surface and easiness of attack. Even if we could trigger an &lt;br /&gt;
exception in an Apache Web</description>
				<link>http://www.garage4hackers.com/content/146-fuzzing-dtmf-detection-algorithms.html</link>
				<guid>http://www.garage4hackers.com/content/146-fuzzing-dtmf-detection-algorithms.html</guid>
			</item>
		
		</channel>
	</rss>