<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>firefoxurl: URL vulnerability</title><link>http://msmvps.com/blogs/alunj/archive/2007/07/22/firefoxurl-url-vulnerability.aspx</link><description>Heard about the firefoxurl vulnerability? It turns out that you can exploit Firefox by having Internet Explorer visit a link to a URL that starts with &amp;quot;firefoxurl:&amp;quot; (and a bunch of other code). [Assuming you have Firefox on your computer along</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>re: firefoxurl: URL vulnerability</title><link>http://msmvps.com/blogs/alunj/archive/2007/07/22/firefoxurl-url-vulnerability.aspx#1202899</link><pubDate>Mon, 17 Sep 2007 22:06:54 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1202899</guid><dc:creator>unoqueva</dc:creator><description>&lt;p&gt;ie seems vuln too...&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.kriptopolis.org/robo-identidades-secondlife-con-explorer"&gt;www.kriptopolis.org/robo-identidades-secondlife-con-explorer&lt;/a&gt;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1202899" width="1" height="1"&gt;</description></item><item><title>re: firefoxurl: URL vulnerability</title><link>http://msmvps.com/blogs/alunj/archive/2007/07/22/firefoxurl-url-vulnerability.aspx#1062270</link><pubDate>Fri, 27 Jul 2007 21:22:43 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1062270</guid><dc:creator>Alun Jones</dc:creator><description>&lt;p&gt;While I think you are probably right that encoding everything except reserved characters, alphanumerics and percent would be safe from double-decoding, that's not what the RFC actually says. By the time the browser hits it, the URI should be presumed to have already been encoded, and encoding any part of the string would be considered to be doubly encoding.&lt;/p&gt;
&lt;p&gt;I reiterate - if you're going to re-encode the string, you should re-encode the whole string - all characters that are not reserved, percent or alphanumeric. By that standard, Mozilla has not implemented an elegant solution, and runs the risk that some other character sequence (not to mention the possibility of Unicode) will cause them the same problem in the future.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1062270" width="1" height="1"&gt;</description></item><item><title>re: firefoxurl: URL vulnerability</title><link>http://msmvps.com/blogs/alunj/archive/2007/07/22/firefoxurl-url-vulnerability.aspx#1052883</link><pubDate>Tue, 24 Jul 2007 14:43:27 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1052883</guid><dc:creator>Giorgio Maone</dc:creator><description>&lt;p&gt;&amp;quot;[...] Implementations must not percent-encode or decode the same string more than once, as decoding an already decoded string might lead to misinterpreting a percent data octet as the beginning of a percent-encoding [...]&amp;quot;&lt;/p&gt;
&lt;p&gt;This means an implementation *may* attempt to *partially* encode characters which have been left unencoded against the spec in an URL supposed to be ready for consumption (as the one which is going out through external protocol handlers). As a matter of fact, it may try to encode anything but the percent octet and the reserved characters.&lt;/p&gt;
&lt;p&gt;Such an interpretation perfectly justify the (very simple but effective) fix that&amp;#39;s already been implemented by Mozilla guys, see &lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=389106" target="_new" rel="nofollow"&gt;bugzilla.mozilla.org/show_bug.cgi&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A similar fix is readily available for NoScript users.&lt;/p&gt;
&lt;p&gt;--&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a browser safer than Firefox... &lt;a href="http://noscript.net/" target="_new" rel="nofollow"&gt;http://noscript.net&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1052883" width="1" height="1"&gt;</description></item><item><title>Window Snyder fesses up - Firefox also passes "bad data"</title><link>http://msmvps.com/blogs/alunj/archive/2007/07/22/firefoxurl-url-vulnerability.aspx#1051412</link><pubDate>Tue, 24 Jul 2007 06:11:31 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1051412</guid><dc:creator>Spyware Sucks</dc:creator><description>&lt;p&gt;Window says: &amp;amp;quot;Over the weekend, we learned about a new scenario that identifies ways that Firefox&lt;/p&gt;
&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1051412" width="1" height="1"&gt;</description></item><item><title>re: firefoxurl: URL vulnerability</title><link>http://msmvps.com/blogs/alunj/archive/2007/07/22/firefoxurl-url-vulnerability.aspx#1048315</link><pubDate>Mon, 23 Jul 2007 10:54:32 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1048315</guid><dc:creator>Mosh Jahan</dc:creator><description>&lt;p&gt;Nice one Alun. &amp;nbsp;I&amp;#39;m a die hard IE fan, it&amp;#39;s the best. &amp;nbsp;I went to Firefox for a while for the adblocking plugin but now I&amp;#39;m back with IE using IEPro plugin. &amp;nbsp;Firefox gobbled up so much damn memory at times that I got fed up having to shut it down and restart it every 15 minutes or so.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1048315" width="1" height="1"&gt;</description></item></channel></rss>