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

CWE-20 — Improper Input Validation7 documents7 sources
Severity
5.4MEDIUMNVD
EPSS
0.8%
top 26.22%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
4
Google ChromeChromiumDebian Chromium+1 more
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:L/I:L/A:NExploitability: 2.8 | Impact: 2.5

Affected Packages5 packages

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

🔴Vulnerability Details

2
GHSA
GHSA-c4cg-824h-p857: Insufficient validation of untrusted input in Omnibox in Google Chrome prior to 80↗2022-05-24
▶
OSV
CVE-2020-6411: Insufficient validation of untrusted input in Omnibox in Google Chrome prior to 80↗2020-02-11
▶

📋Vendor Advisories

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

💬Community

1
Bugzilla
CVE-2020-6411 chromium-browser: Insufficient validation of untrusted input in Omnibox↗2020-02-10
▶