Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1342890 - (CVE-2016-2815) CVE-2016-2815 Mozilla: Miscellaneous memory safety hazards (rv:47.0) (MFSA 2016-49)
CVE-2016-2815 Mozilla: Miscellaneous memory safety hazards (rv:47.0) (MFSA 20...
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
urgent Severity urgent
: ---
: ---
Assigned To: Red Hat Product Security
impact=critical,public=20160607,repor...
: Security
Depends On:
Blocks: 1335788
  Show dependency treegraph
 
Reported: 2016-06-06 00:05 EDT by Huzaifa S. Sidhpurwala
Modified: 2016-06-08 23:10 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-06-08 23:10:10 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 Huzaifa S. Sidhpurwala 2016-06-06 00:05:41 EDT
Mozilla developers and community members reported 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.

Christoph Diehl, Julian Hector, Jan de Mooij, Mats Palmgren, and Tooru Fujisawa reported memory safety problems and crashes that are fixed in Firefox 47.


External Reference:

https://www.mozilla.org/security/announce/2016/mfsa2016-49.html


Acknowledgements:

Name: the Mozilla project
Upstream: Christoph Diehl, Julian Hector, Jan de Mooij, Mats Palmgren, and Tooru Fujisawa

Statement:

This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7.

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