Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1503542 - (CVE-2017-15387) CVE-2017-15387 chromium-browser: content security bypass
CVE-2017-15387 chromium-browser: content security bypass
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=20171017,repor...
: Security
Depends On: 1503551 1503557 1503558
Blocks: 1503554
  Show dependency treegraph
 
Reported: 2017-10-18 07:42 EDT by Martin Prpič
Modified: 2017-10-20 04:51 EDT (History)
4 users (show)

See Also:
Fixed In Version: chromium-browser 62.0.3202.62
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-10-20 04:51:25 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-2017:2997 normal SHIPPED_LIVE Important: chromium-browser security update 2017-10-20 08:39:11 EDT

  None (edit)
Description Martin Prpič 2017-10-18 07:42:22 EDT
The following flaw was identified in the Chromium browser: content security bypass.

Upstream bug(s):

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

External References:

https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html
Comment 1 Martin Prpič 2017-10-18 07:46:10 EDT
Created chromium tracking bugs for this issue:

Affects: fedora-all [bug 1503551]
Comment 3 errata-xmlrpc 2017-10-20 04:41:22 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

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

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