You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.

You are here: Known Vulnerabilities in Mozilla Products (Firefox 2.0.0.2) > MFSA 2007-01

Mozilla Foundation Security Advisory 2007-01

Title: Crashes with evidence of memory corruption (rv:1.8.0.10/1.8.1.2)
Impact: Critical
Announced: February 23, 2007
Reporter: Mozilla developers and community
Products: Firefox, Thunderbird, SeaMonkey

Fixed in: Firefox 2.0.0.2
Firefox 1.5.0.10
Thunderbird 1.5.0.10
SeaMonkey 1.0.8

Description

As part of the Firefox 2.0.0.2 and 1.5.0.10 update releases we fixed several bugs to improve the stability of the product. Some of these were crashes that showed evidence of memory corruption and we presume that with enough effort at least some of these could be exploited to run arbitrary code.

Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Without further investigation we cannot rule out the possibility that for some of these an attacker might be able to prepare memory for exploitation through some means other than JavaScript, such as large images.

Workaround

Upgrade to the fixed versions. Do not enable JavaScript in Thunderbird or the mail portions of SeaMonkey.

References

Jesse Ruderman, Martijn Wargers and Olli Pettay reported crashes in the layout engine

Tom Ferris reported a heap buffer overflow in SVG involving wide stroke widths. This flaw was introduced in Firefox 2 and does not affect earlier releases.

Brian Crowder, Igor Bukanov, Johnny Stenback, moz_bug_r_a4 and shutdown reported potential memory corruption in the JavaScript engine