CVE-2020-6410: High severity Google Chrome vulnerability
An insufficient policy enforcement flaw was found in the navigation component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=881675
External References:
https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html
Other sources
Insufficient policy enforcement in navigation in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to confuse the user 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/browserto a version that resolves this vulnerability.Fixed in 80.0.3987.87
Event History
Frequently Asked Questions
What is the severity of CVE-2020-6410?
CVE-2020-6410 has a medium severity rating due to an insufficient policy enforcement flaw affecting Chromium browser.
How do I fix CVE-2020-6410?
To fix CVE-2020-6410, update your Chromium browser to version 80.0.3987.87 or later.
Which versions of Chromium are affected by CVE-2020-6410?
CVE-2020-6410 affects Chromium versions prior to 80.0.3987.87.
Is CVE-2020-6410 present in Google Chrome?
Yes, CVE-2020-6410 impacts Google Chrome versions prior to 80.0.3987.87.
Who reported CVE-2020-6410?
CVE-2020-6410 was reported through upstream bug tracking for the Chromium project.