CVE-2020-6401: Input Validation
An insufficient validation of untrusted input flaw was found in the Omnibox component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=1017707
External References:
https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html
Other sources
Insufficient validation of untrusted input in Omnibox in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to perform domain spoofing via IDN homographs 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/omniboxto a version that resolves this vulnerability.Fixed in 80.0.3987.87
Event History
Frequently Asked Questions
What is the severity of CVE-2020-6401?
CVE-2020-6401 has been rated as a high severity vulnerability due to insufficient validation of untrusted input in the Chromium browser.
How do I fix CVE-2020-6401?
To fix CVE-2020-6401, update to the latest version of the Chromium or Chrome browser that addresses this vulnerability.
Which versions are affected by CVE-2020-6401?
CVE-2020-6401 affects multiple versions of Chromium and Google Chrome prior to 80.0.3987.87.
What is the impact of CVE-2020-6401?
The impact of CVE-2020-6401 may include potential unauthorized access or manipulation of browser data due to insufficient input validation.
Is CVE-2020-6401 being actively exploited?
As of the last update, there are no confirmed reports of CVE-2020-6401 being actively exploited in the wild.