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 1180973 - (CVE-2014-8641) CVE-2014-8641 Mozilla: Read-after-free in WebRTC (MFSA 2015-06)
CVE-2014-8641 Mozilla: Read-after-free in WebRTC (MFSA 2015-06)
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
impact=important,public=20150113,repo...
: Security
Depends On:
Blocks: 1179163
  Show dependency treegraph
 
Reported: 2015-01-12 00:08 EST by Huzaifa S. Sidhpurwala
Modified: 2015-02-27 05:29 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-01-14 05:50:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0046 normal SHIPPED_LIVE Critical: firefox security and bug fix update 2015-01-13 23:18:51 EST

  None (edit)
Description Huzaifa S. Sidhpurwala 2015-01-12 00:08:11 EST
Security researcher Mitchell Harper discovered a read-after-free in WebRTC due to the way tracks are handled. This results in a either a potentially exploitable crash or incorrect WebRTC behavior. 


External Reference:

http://www.mozilla.org/security/announce/2015/mfsa2015-06.html


Acknowledgements:

Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mitchell Harper as the original reporter.
Comment 1 errata-xmlrpc 2015-01-13 18:19:37 EST
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6
  Red Hat Enterprise Linux 5
  Red Hat Enterprise Linux 7

Via RHSA-2015:0046 https://rhn.redhat.com/errata/RHSA-2015-0046.html

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