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 1538523 - (CVE-2018-6051) CVE-2018-6051 chromium-browser: referrer leak in xss auditor
CVE-2018-6051 chromium-browser: referrer leak in xss auditor
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20180124,reported=2...
: Security
Depends On: 1538531 1538530 1538532 1538533
Blocks: 1538571
  Show dependency treegraph
 
Reported: 2018-01-25 03:50 EST by Adam Mariš
Modified: 2018-02-01 14:46 EST (History)
3 users (show)

See Also:
Fixed In Version: chromium-browser 64.0.3282.119
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-02-01 14:46:16 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-2018:0265 normal SHIPPED_LIVE Important: chromium-browser security update 2018-02-01 16:06:57 EST

  None (edit)
Description Adam Mariš 2018-01-25 03:50:53 EST
A referrer leak flaw was found in the XSS Auditor component of the Chromium browser.

Upstream bug(s):

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

External References:

https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html
Comment 1 Adam Mariš 2018-01-25 04:00:19 EST
Created chromium tracking bugs for this issue:

Affects: epel-7 [bug 1538531]
Affects: fedora-all [bug 1538533]
Comment 3 errata-xmlrpc 2018-02-01 11:08:57 EST
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

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

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