Bug 576698 (CVE-2010-0167)

Summary: CVE-2010-0167 firefox/thunderbird/seamonkey: crashes with evidence of memory corruption (MFSA 2010-11)
Product: [Other] Security Response Reporter: Vincent Danen <vdanen>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: unspecifiedCC: caillon, desktop-bugs, gecko-bugs-nobody, gecko-bugs-nobody, stransky
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0167
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-24 23:00:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vincent Danen 2010-03-24 21:08:56 UTC
Mozilla developers identified and fixed several stability bugs in the
browser engine used in Firefox and other Mozilla-based products. Some of
these crashes 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.

This MFSA addresses several CVEs; all but one are specific to Firefox 3.6.

Bob Clary and Carsten Book reported crashes in the browser engine which
affected all supported versions of the browser engine. (CVE-2010-0167)

Upstream advisory:

http://www.mozilla.org/security/announce/2010/mfsa2010-11.html

This was fixed in upstream Firefox 3.0.18, and via RHSA-2010:0112 in Red Hat
Enterprise Linux 4 and 5.

https://rhn.redhat.com/errata/RHSA-2010-0112.html

Comment 2 Vincent Danen 2010-03-24 23:00:43 UTC
This issue only affects Thunderbird and Seamonkey builds based on Gecko 1.9.  The Thunderbird and Seamonkey versions as provided with Red Hat Enterprise Linux 3, 4, and 5 are based on Gecko 1.8, so they are not vulnerable to this issue.