<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: -82DAY: NoScript pwns Quicktime pwning Firefox</title>
	<link>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/</link>
	<description>Giorgio Maone's answers to the Web, the Universe, and Everything</description>
	<pubDate>Wed, 16 May 2012 17:16:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Eve</title>
		<link>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-7542</link>
		<dc:creator>Eve</dc:creator>
		<pubDate>Wed, 02 Apr 2008 19:16:26 +0000</pubDate>
		<guid>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-7542</guid>
		<description>Funnily enough (nothing to do with the post that is scary enough) that pic is on display at the Amsterdam "Torture Museum". Visited it last month!

Small world...</description>
		<content:encoded><![CDATA[<p>Funnily enough (nothing to do with the post that is scary enough) that pic is on display at the Amsterdam &#8220;Torture Museum&#8221;. Visited it last month!</p>
<p>Small world&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Old NoScript Tricks Blocking New Vulnerabilities &#124; CorrectServer.com - Servers and Server Software</title>
		<link>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-5044</link>
		<dc:creator>Old NoScript Tricks Blocking New Vulnerabilities &#124; CorrectServer.com - Servers and Server Software</dc:creator>
		<pubDate>Wed, 23 Jan 2008 16:12:01 +0000</pubDate>
		<guid>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-5044</guid>
		<description>[...] It happened in the past and it’s happening again: a new directory traversal vulnerability with potential for private data exposure has been publicly disclosed and confirmed by Mozilla, but NoScript users have been protected since August 2007. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] It happened in the past and it’s happening again: a new directory traversal vulnerability with potential for private data exposure has been publicly disclosed and confirmed by Mozilla, but NoScript users have been protected since August 2007. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hackademix.net » Old NoScript Tricks Blocking New Vulnerabilities</title>
		<link>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-5041</link>
		<dc:creator>hackademix.net » Old NoScript Tricks Blocking New Vulnerabilities</dc:creator>
		<pubDate>Wed, 23 Jan 2008 14:15:51 +0000</pubDate>
		<guid>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-5041</guid>
		<description>[...] It happened in the past and it&#8217;s happening again: a new directory traversal vulnerability with potential for private data exposure has been publicly disclosed and confirmed by Mozilla, but NoScript users are protected since August 2007. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] It happened in the past and it&#8217;s happening again: a new directory traversal vulnerability with potential for private data exposure has been publicly disclosed and confirmed by Mozilla, but NoScript users are protected since August 2007. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hackademix.net » Java, Quicktime and Other Good News</title>
		<link>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-609</link>
		<dc:creator>hackademix.net » Java, Quicktime and Other Good News</dc:creator>
		<pubDate>Thu, 04 Oct 2007 05:29:15 +0000</pubDate>
		<guid>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-609</guid>
		<description>[...] &#8220;Quicktime pwns default browsers&#8221; bug, after being worked around by Mozilla with the release of Firefox 2.0.0.7, has been [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] &#8220;Quicktime pwns default browsers&#8221; bug, after being worked around by Mozilla with the release of Firefox 2.0.0.7, has been [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hackademix.net » Don't Open That Doc!</title>
		<link>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-409</link>
		<dc:creator>hackademix.net » Don't Open That Doc!</dc:creator>
		<pubDate>Thu, 20 Sep 2007 19:55:49 +0000</pubDate>
		<guid>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-409</guid>
		<description>[...] seen MP3 tunes pwning Firefox (and NoScript promptly counter-pwning), Windows playlists pwning browser security, and finally PDF documents pwning Windows PCs. This [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] seen MP3 tunes pwning Firefox (and NoScript promptly counter-pwning), Windows playlists pwning browser security, and finally PDF documents pwning Windows PCs. This [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ·¨-=[WHK]=-¨· &#187; Archive &#187; Zero day en QuickTime de apple permite la ejecución de códigos remotamente (</title>
		<link>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-371</link>
		<dc:creator>·¨-=[WHK]=-¨· &#187; Archive &#187; Zero day en QuickTime de apple permite la ejecución de códigos remotamente (</dc:creator>
		<pubDate>Fri, 14 Sep 2007 19:43:01 +0000</pubDate>
		<guid>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-371</guid>
		<description>[...] hackademix.net » -82DAY: NoScript pwns Quicktime pwning Firefox [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] hackademix.net » -82DAY: NoScript pwns Quicktime pwning Firefox [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quicktime bug dangerous for Firefox users &#171;</title>
		<link>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-365</link>
		<dc:creator>Quicktime bug dangerous for Firefox users &#171;</dc:creator>
		<pubDate>Thu, 13 Sep 2007 04:48:57 +0000</pubDate>
		<guid>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-365</guid>
		<description>[...] users can protect themselves against this exploit by using the NoScript extension. According to this post at hackademix.net, the addon will prevent Petkov&#8217;s exploit from working even if a user has [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] users can protect themselves against this exploit by using the NoScript extension. According to this post at hackademix.net, the addon will prevent Petkov&#8217;s exploit from working even if a user has [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Giorgio</title>
		<link>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-364</link>
		<dc:creator>Giorgio</dc:creator>
		<pubDate>Thu, 13 Sep 2007 03:40:08 +0000</pubDate>
		<guid>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-364</guid>
		<description>@&lt;b&gt;hmm&lt;/b&gt;:
You wrote:
&lt;blockquote&gt;
ever thought about just overhauling the javascript engine in firefox to only exec the known good instead of the known bad?
[...]limiting the function calls implementing in the ff javascript stack to a discrete few[...]
&lt;/blockquote&gt;
Can you show me what's "known good" and what's "known bad" with JavaScript?
It's a &lt;a href="http://en.wikipedia.org/wiki/Turing_complete" rel="external nofollow" target="_blank" rel="nofollow"&gt;Turing complete&lt;/a&gt;, &lt;a href="http://en.wikipedia.org/wiki/Dynamic_language" rel="external nofollow" rel="nofollow"&gt;dynamic&lt;/a&gt; and the browser DOM allows it to do the same thing in &lt;a href="http://hackademix.net/2007/09/04/phpids-threesome/" rel="nofollow"&gt;a million of ways&lt;/a&gt;, so good luck with that.
Just to stay with the DOM API, I'd just not know where to start: XMLHttpRequest? document.cookie? window.location? Image? node.innerHTML? document.createNode?
Any suggestion is welcome...

@&lt;b&gt;bugstomper&lt;/b&gt;:
you're right, it doesn't work on Mac OS X and the reason is quite clear. I'm updating my post to reflect this.</description>
		<content:encoded><![CDATA[<p>@<b>hmm</b>:<br />
You wrote:</p>
<blockquote><p>
ever thought about just overhauling the javascript engine in firefox to only exec the known good instead of the known bad?<br />
[&#8230;]limiting the function calls implementing in the ff javascript stack to a discrete few[&#8230;]
</p></blockquote>
<p>Can you show me what&#8217;s &#8220;known good&#8221; and what&#8217;s &#8220;known bad&#8221; with JavaScript?<br />
It&#8217;s a <a href="http://en.wikipedia.org/wiki/Turing_complete" rel="external nofollow" target="_blank" rel="nofollow">Turing complete</a>, <a href="http://en.wikipedia.org/wiki/Dynamic_language" rel="external nofollow" rel="nofollow">dynamic</a> and the browser DOM allows it to do the same thing in <a href="http://hackademix.net/2007/09/04/phpids-threesome/" rel="nofollow">a million of ways</a>, so good luck with that.<br />
Just to stay with the DOM API, I&#8217;d just not know where to start: XMLHttpRequest? document.cookie? window.location? Image? node.innerHTML? document.createNode?<br />
Any suggestion is welcome&#8230;</p>
<p>@<b>bugstomper</b>:<br />
you&#8217;re right, it doesn&#8217;t work on Mac OS X and the reason is quite clear. I&#8217;m updating my post to reflect this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bugstomper</title>
		<link>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-361</link>
		<dc:creator>bugstomper</dc:creator>
		<pubDate>Thu, 13 Sep 2007 00:19:13 +0000</pubDate>
		<guid>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-361</guid>
		<description>The proof of concept doesn't work on my Firefox 2.0.0.6 under MacOS 10.4.9, and I don't have NoScript installed. When I try his POC, I first get an alert telling me that I'm trying to authenticate as username chrome%20javascript on site mozilla.org that does not require authentication, it may be an attempt to trick me, and asking if mozilla.org is the site I want to visit. Even if I click Yes, the resulting URL is not a chrome one, but is http://mozilla.org/.... followed by what looks like the attempted exploit code. Instead of running the exploit, that simply results in a 404 not found error from mozilla.org.

pdp says on his site that the vulnerability is cross-platform, and I see everyone quoting him on that, but he also said he doesn't have a Mac and hasn't tried it on one.</description>
		<content:encoded><![CDATA[<p>The proof of concept doesn&#8217;t work on my Firefox 2.0.0.6 under MacOS 10.4.9, and I don&#8217;t have NoScript installed. When I try his POC, I first get an alert telling me that I&#8217;m trying to authenticate as username chrome%20javascript on site mozilla.org that does not require authentication, it may be an attempt to trick me, and asking if mozilla.org is the site I want to visit. Even if I click Yes, the resulting URL is not a chrome one, but is <a href="http://mozilla.org/...." rel="nofollow">http://mozilla.org/&#8230;.</a> followed by what looks like the attempted exploit code. Instead of running the exploit, that simply results in a 404 not found error from mozilla.org.</p>
<p>pdp says on his site that the vulnerability is cross-platform, and I see everyone quoting him on that, but he also said he doesn&#8217;t have a Mac and hasn&#8217;t tried it on one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: securology</title>
		<link>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-359</link>
		<dc:creator>securology</dc:creator>
		<pubDate>Wed, 12 Sep 2007 13:48:24 +0000</pubDate>
		<guid>http://hackademix.net/2007/09/12/noscript-pwns-quicktime-pwning-firefox/#comment-359</guid>
		<description>&lt;strong&gt;Another separation of code and data issue ...&lt;/strong&gt;

Again. Just another example of why it is important to separate executable code from data objects ...</description>
		<content:encoded><![CDATA[<p><strong>Another separation of code and data issue &#8230;</strong></p>
<p>Again. Just another example of why it is important to separate executable code from data objects &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

