Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1393732 - (CVE-2016-5200) CVE-2016-5200 chromium-browser: out of bounds memory access in v8
CVE-2016-5200 chromium-browser: out of bounds memory access in v8
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=20161109,repo...
: Security
Depends On: 1393737 1393738 1393739
Blocks: 1393735
  Show dependency treegraph
 
Reported: 2016-11-10 03:53 EST by Adam Mariš
Modified: 2016-11-14 15:51 EST (History)
4 users (show)

See Also:
Fixed In Version: Chrome 54.0.2840.99
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-14 15:51:05 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-2016:2718 normal SHIPPED_LIVE Important: chromium-browser security update 2016-11-14 20:04:03 EST

  None (edit)
Description Adam Mariš 2016-11-10 03:53:44 EST
An out of bounds memory access flaw was found in the V8 component of the Chromium browser.

Upstream bug(s):

https://code.google.com/p/chromium/issues/detail?id=658114

External References:

https://googlechromereleases.blogspot.com/2016/11/stable-channel-update-for-desktop_9.html
Comment 1 Adam Mariš 2016-11-10 03:56:11 EST
Created chromium tracking bugs for this issue:

Affects: fedora-all [bug 1393737]
Comment 3 errata-xmlrpc 2016-11-14 15:06:25 EST
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

Via RHSA-2016:2718 https://rhn.redhat.com/errata/RHSA-2016-2718.html

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