Bug 576698 - (CVE-2010-0167) CVE-2010-0167 firefox/thunderbird/seamonkey: crashes with evidence of memory corruption (MFSA 2010-11)
CVE-2010-0167 firefox/thunderbird/seamonkey: crashes with evidence of memory ...
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
urgent Severity urgent
: ---
: ---
Assigned To: Red Hat Product Security
http://web.nvd.nist.gov/view/vuln/det...
impact=critical,source=internet,repor...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-03-24 17:08 EDT by Vincent Danen
Modified: 2010-03-25 05:49 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-03-24 19:00:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vincent Danen 2010-03-24 17:08:56 EDT
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 19:00:43 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.