Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1462151 - (CVE-2017-5089) CVE-2017-5089 chromium-browser: domain spoofing in omnibox
CVE-2017-5089 chromium-browser: domain spoofing in omnibox
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=20170615,repor...
: Security
Depends On: 1462154 1462156 1462157
Blocks: 1462152
  Show dependency treegraph
 
Reported: 2017-06-16 06:36 EDT by Adam Mariš
Modified: 2017-06-19 06:50 EDT (History)
3 users (show)

See Also:
Fixed In Version: Chrome 59.0.3071.104
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-06-19 06:50:12 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:1495 normal SHIPPED_LIVE Important: chromium-browser security update 2017-06-19 10:21:31 EDT

  None (edit)
Description Adam Mariš 2017-06-16 06:36:05 EDT
A domain spoofing flaw was found in the Omnibox component of the Chromium browser.

Upstream bug(s):

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

External References:

https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop_15.html
Comment 1 Adam Mariš 2017-06-16 06:38:27 EDT
Created chromium tracking bugs for this issue:

Affects: fedora-all [bug 1462154]
Comment 3 errata-xmlrpc 2017-06-19 06:22:04 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

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

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