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 1552486 - (CVE-2018-6069) CVE-2018-6069 chromium-browser: stack buffer overflow in skia
CVE-2018-6069 chromium-browser: stack buffer overflow in skia
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180306,repor...
: Security
Depends On: 1552501 1552502 1552503 1552504
Blocks: 1552510
  Show dependency treegraph
 
Reported: 2018-03-07 03:29 EST by Andrej Nemec
Modified: 2018-03-12 15:59 EDT (History)
3 users (show)

See Also:
Fixed In Version: chromium-browser 65.0.3325.146
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-12 15:59:19 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0484 normal SHIPPED_LIVE Important: chromium-browser security update 2018-03-12 18:21:28 EDT

  None (edit)
Description Andrej Nemec 2018-03-07 03:29:39 EST
A stack buffer overflow flaw was found in the Skia component of the Chromium browser.

Upstream bug(s):

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

External References:

https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html
Comment 1 Andrej Nemec 2018-03-07 03:35:28 EST
Created chromium tracking bugs for this issue:

Affects: fedora-all [bug 1552502]
Affects: epel-7 [bug 1552504]
Comment 3 errata-xmlrpc 2018-03-12 14:07:41 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

Via RHSA-2018:0484 https://access.redhat.com/errata/RHSA-2018:0484

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