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 1510429 - (CVE-2017-15398) CVE-2017-15398 chromium-browser: stack buffer overflow in quic
CVE-2017-15398 chromium-browser: stack buffer overflow in quic
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
impact=critical,public=20171106,repor...
: Security
Depends On: 1510434 1510435 1510436
Blocks: 1510433
  Show dependency treegraph
 
Reported: 2017-11-07 07:01 EST by Adam Mariš
Modified: 2017-11-07 16:35 EST (History)
4 users (show)

See Also:
Fixed In Version: Chrome 62.0.3202.89
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-07 16:35: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-2017:3151 normal SHIPPED_LIVE Critical: chromium-browser security update 2017-11-07 20:58:59 EST

  None (edit)
Description Adam Mariš 2017-11-07 07:01:35 EST
A stack buffer overflow flaw was found in the QUIC component of the Chromium browser.

Upstream bug(s):

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

External References:

https://chromereleases.googleblog.com/2017/11/stable-channel-update-for-desktop.html
Comment 1 Adam Mariš 2017-11-07 07:02:56 EST
Created chromium tracking bugs for this issue:

Affects: fedora-all [bug 1510434]
Comment 3 errata-xmlrpc 2017-11-07 15:59:21 EST
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

Via RHSA-2017:3151 https://access.redhat.com/errata/RHSA-2017:3151

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