<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Safari 3.2.2 Feed Protocol Handler Issues</title>
	<atom:link href="http://xs-sniper.com/blog/2009/06/09/safari-322-feed-protocol-handler-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://xs-sniper.com/blog/2009/06/09/safari-322-feed-protocol-handler-issues/</link>
	<description>Thoughts on Security in an Uncivilized World…</description>
	<lastBuildDate>Wed, 08 Sep 2010 02:39:08 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Ur Face</title>
		<link>http://xs-sniper.com/blog/2009/06/09/safari-322-feed-protocol-handler-issues/comment-page-1/#comment-837</link>
		<dc:creator>Ur Face</dc:creator>
		<pubDate>Sat, 17 Oct 2009 01:28:51 +0000</pubDate>
		<guid isPermaLink="false">http://xs-sniper.com/blog/?p=265#comment-837</guid>
		<description>Dude, Safari sucks. IE is the shite!!!!! 

GO IE! 

Plus, Apple is about to be the most pwnd OS per capita.</description>
		<content:encoded><![CDATA[<p>Dude, Safari sucks. IE is the shite!!!!! </p>
<p>GO IE! </p>
<p>Plus, Apple is about to be the most pwnd OS per capita.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Security: Script Injection in Safari 3.2.2 &#171; Nitin Katkam</title>
		<link>http://xs-sniper.com/blog/2009/06/09/safari-322-feed-protocol-handler-issues/comment-page-1/#comment-831</link>
		<dc:creator>Security: Script Injection in Safari 3.2.2 &#171; Nitin Katkam</dc:creator>
		<pubDate>Mon, 21 Sep 2009 16:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://xs-sniper.com/blog/?p=265#comment-831</guid>
		<description>[...] A blog post from a couple of months ago by Billy Rios mentions about a security bug affecting Safari 3.2.2. Although Safari checks content for the presence of SCRIPT tags within the markup, they somehow forgot to do that for the summary attribute of a feed. As scripts present within the content of a document with a feed URI scheme run with elevated privileges, it is possible to inject a script that can retrieve a document stored on the user&#8217;s hard drive and upload it to a web server. For a code snippet of how this can be performed, go to the blog article by Billy Rios. [...]</description>
		<content:encoded><![CDATA[<p>[...] A blog post from a couple of months ago by Billy Rios mentions about a security bug affecting Safari 3.2.2. Although Safari checks content for the presence of SCRIPT tags within the markup, they somehow forgot to do that for the summary attribute of a feed. As scripts present within the content of a document with a feed URI scheme run with elevated privileges, it is possible to inject a script that can retrieve a document stored on the user&#8217;s hard drive and upload it to a web server. For a code snippet of how this can be performed, go to the blog article by Billy Rios. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Mastenbrook</title>
		<link>http://xs-sniper.com/blog/2009/06/09/safari-322-feed-protocol-handler-issues/comment-page-1/#comment-805</link>
		<dc:creator>Brian Mastenbrook</dc:creator>
		<pubDate>Thu, 02 Jul 2009 17:48:15 +0000</pubDate>
		<guid isPermaLink="false">http://xs-sniper.com/blog/?p=265#comment-805</guid>
		<description>I couldn&#039;t find an obvious contact email on your site, but I thought I&#039;d drop you a line in a comment to provide a little more information about an issue that Apple fixed in the 2009-001 update, in case you&#039;re interested. The issue I reported was mentioned as part of the same advisory as the one you wrote about in &quot;Stealing More Files with Safari&quot;, and the impact was the same, but the mechanism I used was a little different. Prior to the 2009-001 update, Safari rendered any content returned with a 404 or other error-status page in a feed:// handler as if it was in the local content zone.

I&#039;m not surprised that a slight variant of the original issue remained unfixed, either. I think I&#039;m on round 4 of trying to fix &#039;help:&#039; URL vulnerabilities in OS X with them. It&#039;s become very clear that their approach to security is driven by &quot;image management&quot; much more so than any sort of thorough procedure.</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t find an obvious contact email on your site, but I thought I&#8217;d drop you a line in a comment to provide a little more information about an issue that Apple fixed in the 2009-001 update, in case you&#8217;re interested. The issue I reported was mentioned as part of the same advisory as the one you wrote about in &#8220;Stealing More Files with Safari&#8221;, and the impact was the same, but the mechanism I used was a little different. Prior to the 2009-001 update, Safari rendered any content returned with a 404 or other error-status page in a feed:// handler as if it was in the local content zone.</p>
<p>I&#8217;m not surprised that a slight variant of the original issue remained unfixed, either. I think I&#8217;m on round 4 of trying to fix &#8216;help:&#8217; URL vulnerabilities in OS X with them. It&#8217;s become very clear that their approach to security is driven by &#8220;image management&#8221; much more so than any sort of thorough procedure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lowan</title>
		<link>http://xs-sniper.com/blog/2009/06/09/safari-322-feed-protocol-handler-issues/comment-page-1/#comment-804</link>
		<dc:creator>Lowan</dc:creator>
		<pubDate>Thu, 02 Jul 2009 07:30:20 +0000</pubDate>
		<guid isPermaLink="false">http://xs-sniper.com/blog/?p=265#comment-804</guid>
		<description>Same on mshtml :).
You can see it by example with RssReader who display your alert =).

L.</description>
		<content:encoded><![CDATA[<p>Same on mshtml <img src='http://xs-sniper.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .<br />
You can see it by example with RssReader who display your alert =).</p>
<p>L.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.372 seconds -->
