CVE-2017-15425: Input Validation
An url spoof flaw was found in the Omnibox component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=756456
External References:
https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html
Other sources
Insufficient policy enforcement in Omnibox in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to perform domain spoofing via IDN homographs in a crafted domain name.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/chromium-browserto a version that resolves this vulnerability.Fixed in 63.0.3239.84 - Upgrade
Upgrade
Google Chrome/Chromiumto a version that resolves this vulnerability.Fixed in 63.0.3239.84
Event History
Frequently Asked Questions
What is the severity of CVE-2017-15425?
CVE-2017-15425 has been rated as high severity due to its potential for exploitation via url spoofing.
How do I fix CVE-2017-15425?
To remediate CVE-2017-15425, update the Chromium browser to version 63.0.3239.84 or later.
Which versions of Chromium are affected by CVE-2017-15425?
CVE-2017-15425 affects Chromium versions prior to 63.0.3239.84.
Can CVE-2017-15425 affect my system if I am using a different browser?
CVE-2017-15425 specifically impacts the Chromium browser, so it does not affect systems using other browsers.
Is there a workaround for CVE-2017-15425 if I cannot upgrade?
There are no specific workarounds for CVE-2017-15425; upgrading is the recommended approach to mitigate the vulnerability.