Mozilla plugs Firefox code execution holes

Mozilla today shipped Firefox 3.0.7 with fixes for at least eight security flaws, some rated critical.
Written by Ryan Naraine, Contributor

Mozilla today shipped Firefox 3.0.7 with fixes for at least eight security flaws, some rated critical.

The most serious of the vulnerabilities could be exploited by attackers to run code and install software, requiring no user interaction beyond normal browsing, Mozilla warned in a series of security advisories.

Here's the skinny on the latest batch of Firefox band-aids:

[ SEE: Talking Firefox security with Mozilla’s Window Snyder ]

  • MFSA 2009-11 (Low risk) Mozilla contributor Masahiro Yamada reported that certain invisible control characters were being decoded when displayed in the location bar, resulting in fewer visible characters than were present in the actual location. An attacker could use this vulnerability to spoof the location bar and display a misleading URL for their malicious web page.
  • MFSA 2009-10(Critical) libpng maintainer Glenn Randers-Pehrson reported several memory safety hazards in PNG libraries used by Mozilla. These vulnerabilities could be used by a malicious website to crash a victim's browser and potentially execute arbitrary code on their computer. libpng was upgraded to a version which contained fixes for these flaws.
  • MFSA 2009-09 (High risk) Mozilla security researcher Georgi Guninski reported that a website could use nsIRDFService and a cross-domain redirect to steal arbitrary XML data from another domain, a violation of the same-origin policy. This vulnerability could be used by a malicious website to steal private data from users authenticated to the redirected website.
  • MFSA 2009-08(Critical) An anonymous researcher, via TippingPoint's Zero Day Initiative program, reported a vulnerability in Mozilla's garbage collection process. The vulnerability was caused by improper memory management of a set of cloned XUL DOM elements which were linked as a parent and child. After reloading the browser on a page with such linked elements, the browser would crash when attempting to access an object which was already destroyed. An attacker could use this crash to run arbitrary code on the victim's computer.
  • MFSA 2009-07 (Critical)  Four different vulnerabilities leading to browser crashes with evidence of memory corruption.

Editorial standards