Mozilla Firefox 3.5.1 to 3.5.2, What's New, Known Issues, & Security Advisories

Firefox Stop Cruelty

Mozilla released Mozilla Firefox v.3.5.2 on August 3rd, 2009. Let’s check out some known issues and security advisories about this latest Firefox release.

According to Mozilla Firefox 3.5.2 Release Notes, the previous version (may v.3.5 or v.3.5.1) has unproper render for images with ICC profile. This latest version now fixes this issues and also several security advisories.

The security issues which fixed in Firefox 3.5.2 are

• MFSA 2009-46 (Critical) – Chrome privilege escalation due to incorrectly cached wrapper
  Mozilla add-on developer and community member Wladimir Palant reported broken functionality on pages that had a Link: HTTP header when an add-on was installed which implemented a Content Policy in JavaScript, such as AdBlock Plus or NoScript. Mozilla security researcher moz_bug_r_a4 demonstrated that the broken functionality was due to the window‘s global object receiving an incorrect security wrapper and that this issue could be used to execute arbitrary JavaScript with chrome privileges.
  Note: This vulnerability does not affect Firefox prior to version 3.5
  This security Advisory was fixed in Firefox 3.5.2
• MFSA 2009-45 (Critical) – Crashes with evidence of memory corruption (rv:1.9.1.2/1.9.0.13)
  Mozilla developers and community members identified and fixed several stability bugs in the browser engine used in Firefox and other Mozilla-based products. Some of these crashes showed evidence of memory corruption under certain circumstances and we presume that with enough effort at least some of these could be exploited to run arbitrary code.
  This security Advisory was fixed in Firefox 3.5.2 and Firefox 3.0.13
• MFSA 2009-44 (Medium) – Location bar and SSL indicator spoofing via window.open() on invalid URL
  Security researcher Juan Pablo Lopez Yacubian reported that an attacker could call window.open() on an invalid URL which looks similar to a legitimate URL and then use document.write() to place content within the new document, appearing to have come from the spoofed location. Additionally, if the spoofed document was created by a document with a valid SSL certificate, the SSL indicators would be carried over into the spoofed document. An attacker could use these issues to display misleading location and SSL information for a malicious web page.
  This security Advisory was fixed in Firefox 3.5.2 and Firefox 3.0.13
• MFSA 2009-38 (Low) – Data corruption with SOCKS5 reply containing DNS name longer than 15 characters
  Andrej Andolsek reported that when Firefox receives a reply from a SOCKS5 proxy which contains a DNS name longer than 15 characters, the subsequent data stream in the response can become corrupted. There was no evidence of memory corruption, however, and the severity of the issue was determined to be low.
  This security Advisory was fixed in Firefox 3.5.2 and Firefox 3.0.12