<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Soroush Dalili - Computer Security Is My Interest! &#187; Opera Browser Scroll Information Leakage</title>
	<atom:link href="http://soroush.secproject.com/blog/tag/opera-browser-scroll-information-leakage/feed/" rel="self" type="application/rss+xml" />
	<link>http://soroush.secproject.com/blog</link>
	<description>Soroush Dalili&#039;s blog - بلاگ سروش دلیلی</description>
	<lastBuildDate>Tue, 10 Jan 2012 22:54:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Opera Browser  &#8211; Scroll Information Leakage</title>
		<link>http://soroush.secproject.com/blog/2010/06/opera-browser-scroll-information-leakage/</link>
		<comments>http://soroush.secproject.com/blog/2010/06/opera-browser-scroll-information-leakage/#comments</comments>
		<pubDate>Wed, 30 Jun 2010 00:10:35 +0000</pubDate>
		<dc:creator>Soroush Dalili</dc:creator>
				<category><![CDATA[My Advisories]]></category>
		<category><![CDATA[Opera Browser Scroll Information Leakage]]></category>

		<guid isPermaLink="false">http://soroush.secproject.com/blog/?p=253</guid>
		<description><![CDATA[In Opera Browser, “scrollTop” and “scrollLeft” properties of a frame are accessible through the main page. This may lead to cross site information leakage. Tested Platform: Opera &#60;= 10.54 AND 10.60 RC (Build 3443) Proof of Concept: http://0me.me/demo/opera_scroll_leak/test_scroll.html UPDATE: Why is it really an issue? I think it is one kind of bypassing same origin [...]]]></description>
			<content:encoded><![CDATA[<p>In Opera Browser, “scrollTop” and “scrollLeft” properties of a frame are accessible through the main page. This may lead to cross site information leakage.</p>
<p>Tested Platform: Opera &lt;= 10.54 AND 10.60 RC (Build 3443)</p>
<p>Proof of Concept:</p>
<p><a href="http://0me.me/demo/opera_scroll_leak/test_scroll.html">http://0me.me/demo/opera_scroll_leak/test_scroll.html</a></p>
<p><strong><span style="color: #ff0000;">UPDATE:</span></strong><br />
<strong>Why is it really an issue?</strong></p>
<div>I think it is one kind of bypassing same origin policy. All other famous browsers are secured against this method.</div>
<div>My point is: If you use &#8220;#&#8221; character, you can jump to a certain point of page in case having that Element&#8217;s ID.</div>
<div>It is shown in my proof of concept if you look at:</div>
<div><a href="http://0me.me/demo/opera_scroll_leak/test_scroll.html">http://0me.me/demo/opera_scroll_leak/test_scroll.html</a></div>
<div>I used two URLs with different Element IDs to collect the user&#8217;s information from Facebook:</div>
<div>First, by using the following URL, I can check if the user is logged-in in facebook. It will jump to &#8220;#pass&#8221; point which is only available in case of having login form at the top of the page.</div>
<div><span style="color: #0000ff;"><a href="http://www.facebook.com/Opera?ref=ts&amp;v=wall#pass">http://www.facebook.com/Opera?ref=ts&amp;v=wall#pass</a></span></div>
<div>Then, as there is a SMS subscription on the Opera Browser Wall (http://www.facebook.com/Opera) when you are the fan, I can find it out by using &#8220;#sms_status_subscribe&#8221; in the following URL:</div>
<div><span style="color: #0000ff;"><a href="http://www.facebook.com/Opera?ref=ts&amp;v=wall#sms_status_subscribe">http://www.facebook.com/Opera?ref=ts&amp;v=wall#sms_status_subscribe</a></span></div>
<div><span style="color: #0000ff;"> </span></div>
<div><span style="color: #0000ff;">And that&#8217;s why&#8230;!</span></div>
]]></content:encoded>
			<wfw:commentRss>http://soroush.secproject.com/blog/2010/06/opera-browser-scroll-information-leakage/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

