Mozilla Foundation Security Advisory 2012-19

Miscellaneous memory safety hazards (rv:11.0/ rv:10.0.3 / rv:1.9.2.28)

Announced

March 13, 2012

Reporter

Mozilla developers and community

Impact

Critical

Products

Firefox, Firefox ESR, SeaMonkey, Thunderbird, Thunderbird ESR

Fixed in

• Firefox 11
• Firefox 3.6.28
• Firefox ESR 10.0.3
• SeaMonkey 2.8
• Thunderbird 11
• Thunderbird 3.1.20
• Thunderbird ESR 10.0.3

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.

In general these flaws cannot be exploited through email in the Thunderbird and SeaMonkey products because scripting is disabled, but are potentially a risk in browser or browser-like contexts in those products.

References

Bob Clary reported two bugs that causes crashes that affected Firefox 3.6, Firefox ESR, and Firefox 10.

• Memory safety bugs fixed in Firefox 11, Firefox ESR 10.0.3, and Firefox 3.6
• CVE-2012-0461

Christian Holler, Jesse Ruderman, Nils, Michael Bebenita, Dindog, and David Anderson reported memory safety problems and crashes that affect Firefox ESR and Firefox 10.

• Memory safety bugs fixed in Firefox 11 and Firefox ESR 10.0.3
• CVE-2012-0462

Jeff Walden reported a memory safety problem in the array.join function. This bug was independently reported by Vincenzo Iozzo and Willem Pinckaers via TippingPoint's Zero Day Initiative Pwn2Own contest.

• array.join("") is GC-hazardous
• CVE-2012-0464

Masayuki Nakano reported a memory safety problem that affected Mobile Firefox 10.

• nsWindow for Android doesn't check whether the instance is destroyed or not after dispatching an event
• CVE-2012-0463