CVE-2020-6401 — Improper Input Validation in Google Chrome

CWE-20 — Improper Input Validation8 documents8 sources
Severity
6.5MEDIUMNVD
EPSS
0.8%
top 26.21%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
3
Google ChromeChromiumOpensuse Backports SLE
Timeline
PublishedFeb 11
Latest updateMay 24

Description

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.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:NExploitability: 2.8 | Impact: 3.6

Affected Packages4 packages

▶CVEListV5google/chromeunspecified — 80.0.3987.87
▶NVDgoogle/chrome< 80.0.3987.87
▶Debianchromium/chromium< 80.0.3987.106-1+3

🔴Vulnerability Details

3
GHSA
GHSA-q8qv-f929-fp24: Insufficient validation of untrusted input in Omnibox in Google Chrome prior to 80↗2022-05-24
▶
OSV
CVE-2020-6401: Insufficient validation of untrusted input in Omnibox in Google Chrome prior to 80↗2020-02-11
▶
CVEList
CVE-2020-6401: Insufficient validation of untrusted input in Omnibox in Google Chrome prior to 80↗2020-02-11
▶

📋Vendor Advisories

3
Chrome
Stable Channel Update for Desktop: CVE-2020-6401↗2020-02-04
▶
Red Hat
chromium-browser: Insufficient validation of untrusted input in Omnibox↗2020-02-04
▶
Debian
CVE-2020-6401: chromium - Insufficient validation of untrusted input in Omnibox in Google Chrome prior to ...↗2020
▶

💬Community

1
Bugzilla
CVE-2020-6401 chromium-browser: Insufficient validation of untrusted input in Omnibox↗2020-02-10
▶
CVE-2020-6401 — Improper Input Validation in Google | cvebase