<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Jar on blag</title><link>https://blog.beford.org/tags/jar/</link><description>Recent content in Jar on blag</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 15 Dec 2007 06:14:40 +0000</lastBuildDate><atom:link href="https://blog.beford.org/tags/jar/index.xml" rel="self" type="application/rss+xml"/><item><title>Firefox 2.0.0.10 released</title><link>https://blog.beford.org/2007/11/27/firefox-20010-released/</link><pubDate>Tue, 27 Nov 2007 05:40:52 +0000</pubDate><guid>https://blog.beford.org/2007/11/27/firefox-20010-released/</guid><description>&lt;p&gt;Mozilla Corporation just released &lt;a href="http://www.mozilla-europe.org/es/products/firefox/2.0.0.10/releasenotes/"&gt;Firefox 2.0.0.10&lt;/a&gt; which includes fixes against &lt;a href="https://blog.beford.org/2007/11/10/firefox-jar-protocol-vulnerability/"&gt;JAR uri attacks&lt;/a&gt;. This issue affected browsers that used Gecko engine, a quick check showed me that only &lt;a href="http://kmeleon.sourceforge.net/"&gt;K-meleon&lt;/a&gt; browser was also updated, however there are several Gecko based web browsers that need to get fixed: &lt;a href="http://en.wikipedia.org/wiki/List_of_web_browsers#Gecko-based_browsers"&gt;Gecko-based browsers.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; Let&amp;rsquo;s make that, Firefox 2.0.0.11, which also fixes some regressions.&lt;/p&gt;</description></item><item><title>Firefox jar: Protocol Vulnerability</title><link>https://blog.beford.org/2007/11/10/firefox-jar-protocol-vulnerability/</link><pubDate>Sat, 10 Nov 2007 10:47:45 +0000</pubDate><guid>https://blog.beford.org/2007/11/10/firefox-jar-protocol-vulnerability/</guid><description>&lt;p&gt;I just came across pdp&amp;rsquo;s finding &lt;a href="http://www.gnucitizen.org/blog/web-mayhem-firefoxs-jar-protocol-issues"&gt;jar protocol vulnerability&lt;/a&gt; on Mozilla Firefox, I think its a big issue, and the fact that it has been on &lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=369814"&gt;bugzilla (#369814)&lt;/a&gt; for way more than &lt;a href="http://ha.ckers.org/blog/20070803/mozilla-says-ten-fucking-days/"&gt;ten fuck*ng days&lt;/a&gt; is not a good thing.&lt;/p&gt;
&lt;p&gt;According to pdp, this issue makes vulnerable to Cross-site scripting applications that allow users uploading compressed ZIP, and JAR files. After a couple of minutes messing around the poc&amp;rsquo;s, I figured out that sites with open redirect issues are vulnerable too. I&amp;rsquo;ve created this poc that attacks Gmail, it&amp;rsquo;s based on my previous post and it will only show your contacts list, it&amp;rsquo;s not being logged server side or anything (as some people thought that my previous poc did. Credit to &lt;a href="http://lowtechlive.com/"&gt;tx&lt;/a&gt; for discovering the &lt;a href="http://sla.ckers.org/forum/read.php?3,505,10958#msg-10958"&gt;open redirect issue&lt;/a&gt; used to exploit Google / Firefox):&lt;/p&gt;</description></item><item><title>Google Vulnerability</title><link>https://blog.beford.org/2007/09/24/googlecom-cross-site-scripting-vulnerability/</link><pubDate>Mon, 24 Sep 2007 03:29:26 +0000</pubDate><guid>https://blog.beford.org/2007/09/24/googlecom-cross-site-scripting-vulnerability/</guid><description>&lt;p&gt;Yesterday, I found a new Google.com XSS vulnerability that can be abused to steal information from Gmail accounts, I&amp;rsquo;ve done responsible disclosure of at least 3 vulns to Google, but since I haven&amp;rsquo;t got enough &amp;lsquo;motivation&amp;rsquo;, I&amp;rsquo;ll go full disclosure now.&lt;/p&gt;
&lt;p&gt;The vulnerability exists in Blogspot polls feature, I had already disclosed a vulnerability on this system. The &amp;lsquo;font&amp;rsquo; parameter was not being sanitized before being used inside an STYLE tag, so you could inject IE&amp;rsquo;s expression() and Mozilla&amp;rsquo;s -moz-binding. They fixed it, however they didn&amp;rsquo;t check enough the rest of the code, the new XSS is:&lt;/p&gt;</description></item></channel></rss>