• Roadmap
• Projects
• Coding
  • Module Owners
  • Hacking
  • Get the Source
  • Build It
• Testing
  • Releases
  • Nightly Builds
  • Report A Problem
• Tools
  • Bugzilla
  • Tinderbox
  • Bonsai
  • LXR
• FAQs

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

Mozilla Foundation Security Advisory 2006-64

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

Fixed in: Firefox 1.5.0.7
  Thunderbird 1.5.0.7
  SeaMonkey 1.0.5

Description

As part of the Firefox 1.5.0.7 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.

Workaround

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

References

CVE-2006-4571

Bernd Mielke and Mats Palmgren reported crashes involving tables

• https://bugzilla.mozilla.org/show_bug.cgi?id=339130
• https://bugzilla.mozilla.org/show_bug.cgi?id=339170
• https://bugzilla.mozilla.org/show_bug.cgi?id=339246
• https://bugzilla.mozilla.org/show_bug.cgi?id=343087
• https://bugzilla.mozilla.org/show_bug.cgi?id=344000
• https://bugzilla.mozilla.org/show_bug.cgi?id=346980

Georgi Guninski discovered heap corruption using XSLTProcessor

• https://bugzilla.mozilla.org/show_bug.cgi?id=348511

Igor Bukanov reported potential memory corruption in the JavaScript engine

• https://bugzilla.mozilla.org/show_bug.cgi?id=345967
• https://bugzilla.mozilla.org/show_bug.cgi?id=346968
• https://bugzilla.mozilla.org/show_bug.cgi?id=348532
• https://bugzilla.mozilla.org/show_bug.cgi?id=350312

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

• https://bugzilla.mozilla.org/show_bug.cgi?id=306940
• https://bugzilla.mozilla.org/show_bug.cgi?id=307826
• https://bugzilla.mozilla.org/show_bug.cgi?id=336999
• https://bugzilla.mozilla.org/show_bug.cgi?id=337419
• https://bugzilla.mozilla.org/show_bug.cgi?id=337883
• https://bugzilla.mozilla.org/show_bug.cgi?id=347355
• https://bugzilla.mozilla.org/show_bug.cgi?id=348049
• https://bugzilla.mozilla.org/show_bug.cgi?id=205735
• https://bugzilla.mozilla.org/show_bug.cgi?id=344291
• https://bugzilla.mozilla.org/show_bug.cgi?id=344557
• https://bugzilla.mozilla.org/show_bug.cgi?id=348062
• https://bugzilla.mozilla.org/show_bug.cgi?id=348729
• https://bugzilla.mozilla.org/show_bug.cgi?id=348887
• https://bugzilla.mozilla.org/show_bug.cgi?id=321299
• https://bugzilla.mozilla.org/show_bug.cgi?id=343457
• https://bugzilla.mozilla.org/show_bug.cgi?id=349201
• https://bugzilla.mozilla.org/show_bug.cgi?id=348688

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

• https://bugzilla.mozilla.org/show_bug.cgi?id=344085

---