You are currently viewing a snapshot of 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, please file a bug.

You are here: Known Vulnerabilities in Mozilla Products (Firefox > MFSA 2006-64

Mozilla Foundation Security Advisory 2006-64

Title: Crashes with evidence of memory corruption (rv:
Impact: Critical
Announced: September 14, 2006
Reporter: Mozilla Developers
Products: Firefox, Thunderbird, SeaMonkey

Fixed in: Firefox
  SeaMonkey 1.0.5


As part of the Firefox release 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 at least some of these could be exploited to run arbitrary code with enough effort.

We thank Bernd Mielke, Georgi Guninski, Igor Bukanov, Jesse Ruderman, Martijn Wargers, Mats Palmgren, Olli Pettay, shutdown, and Weston Carloss for discovering and reporting these crashes.

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 or plugin data.


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



Bernd Mielke and Mats Palmgren reported crashes involving tables

Georgi Guninski discovered heap corruption using XSLTProcessor

Igor Bukanov reported potential memory corruption in the JavaScript engine

Jesse Ruderman, Martijn Wargers, Mats Palmgren, Olli Pettay, and Weston Carloss reported crashes involving DHTML

shutdown reported it was still possible to corrupt memory via content-implemented tree views despite the fix for bug 326501