CVE-2020-6409: High severity Google Chrome vulnerability
An inappropriate implementation flaw was found in the Omnibox component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=1037889
External References:
https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html
Other sources
Inappropriate implementation in Omnibox in Google Chrome prior to 80.0.3987.87 allowed a remote attacker who convinced the user to enter a URI to bypass navigation restrictions via a crafted domain name.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 90.0.4430.212-1~deb10u1Fixed in 116.0.5845.180-1~deb11u1Fixed in 120.0.6099.129-1~deb11u1Fixed in 119.0.6045.199-1~deb12u1Fixed in 120.0.6099.129-1~deb12u1Fixed in 120.0.6099.129-1 - Upgrade
Upgrade
redhat/chromium-browserto a version that resolves this vulnerability.Fixed in 80.0.3987.87 - Upgrade
Upgrade
chromium/omnibox (Google Chrome)to a version that resolves this vulnerability.Fixed in 80.0.3987.87
Event History
Frequently Asked Questions
What is the severity of CVE-2020-6409?
CVE-2020-6409 has been assigned a medium severity rating due to its potential impact on the Chromium browser's security.
How do I fix CVE-2020-6409?
To fix CVE-2020-6409, update your Chromium browser to version 80.0.3987.87 or later.
Which versions of Chromium are affected by CVE-2020-6409?
CVE-2020-6409 affects Chromium versions prior to 80.0.3987.87.
What component is involved in CVE-2020-6409?
CVE-2020-6409 involves an inappropriate implementation flaw in the Omnibox component of the Chromium browser.
Is CVE-2020-6409 specific to Google Chrome only?
No, CVE-2020-6409 affects both Chromium and Google Chrome browsers.