Mozilla Foundation Security Advisory 2011-12
Miscellaneous memory safety hazards (rv:2.0.1/ 1.9.2.17/ 1.9.1.19)
- Announced
- April 28, 2011
- Impact
- Critical
- Products
- Firefox, SeaMonkey, Thunderbird
- Fixed in
-
- Firefox 3.5.19
- Firefox 3.6.17
- Firefox 4.0.1
- SeaMonkey 2.0.14
- Thunderbird 3.1.10
Description
Mozilla developers identified and fixed several memory safety bugs in the browser engine used in Firefox and other Mozilla-based products. Some of these bugs 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.
Credits
Mozilla developers Boris Zbarsky, Gary Kwong, Jesse Ruderman, Michael Wu, Nils, Scoobidiver, and Ted Mielczarek reported memory safety issues which affected Firefox 4.
Mozilla developer Scoobidiver reported a memory safety issue which affected Firefox 4 and Firefox 3.6
The web development team of Alcidion reported a crash that affected Firefox 4, Firefox 3.6 and Firefox 3.5.
Ian Beer reported a crash that affected Firefox 4, Firefox 3.6 and Firefox 3.5.
Mozilla developers Bob Clary, Henri Sivonen, Marco Bonardo, Mats Palmgren and Jesse Ruderman reported memory safety issues which affected Firefox 3.6 and Firefox 3.5
Aki Helin reported memory safety issues which affected Firefox 3.6 and Firefox 3.5
- https://bugzilla.mozilla.org/show_bug.cgi?id=619021
- CVE-2011-0074
- https://bugzilla.mozilla.org/show_bug.cgi?id=635977
- CVE-2011-0075
Ian Beer reported memory safety issues which affected Firefox 3.6 and Firefox 3.5
- https://bugzilla.mozilla.org/show_bug.cgi?id=623998
- CVE-2011-0077
- https://bugzilla.mozilla.org/show_bug.cgi?id=635705
- CVE-2011-0078
Martin Barbella reported a memory safety issue which affected Firefox 3.6 and Firefox 3.5.