Bug 1506942 (CVE-2017-15396, CVE-2017-15406) - CVE-2017-15396, CVE-2017-15406 chromium-browser: stack overflow in v8
Summary: CVE-2017-15396, CVE-2017-15406 chromium-browser: stack overflow in v8
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2017-15396, CVE-2017-15406
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1506944 1506945 1506946
Blocks: 1506943
TreeView+ depends on / blocked
 
Reported: 2017-10-27 08:50 UTC by Adam Mariš
Modified: 2021-02-17 01:19 UTC (History)
5 users (show)

Fixed In Version: Chrome 62.0.3202.75
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-30 14:23:19 UTC

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3082 0 normal SHIPPED_LIVE Important: chromium-browser security update 2017-10-30 18:18:13 UTC

Description Adam Mariš 2017-10-27 08:50:24 UTC 
Stack overflow flaws were found in the V8 component of the Chromium browser.

Upstream bug(s):

https://code.google.com/p/chromium/issues/detail?id=770452
https://bugs.chromium.org/p/chromium/issues/detail?id=770450

External References:

https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop_26.html
Comment 1 Adam Mariš 2017-10-27 08:52:01 UTC 
Created chromium tracking bugs for this issue:

Affects: fedora-all [bug 1506944]
Comment 3 errata-xmlrpc 2017-10-30 14:18:38 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

Via RHSA-2017:3082 https://access.redhat.com/errata/RHSA-2017:3082
Comment 4 Stefan Cornelius 2018-05-14 11:19:35 UTC 
Added CVE-2017-15406:
It appears that, when we originally handled this and released the update, this CVE ID was not available/publicly communicated. As it is part of the same fix, I've updated this bug and the relevant RHSA with the CVE ID.
Note You need to log in before you can comment on or make changes to this bug.