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

CWE-20 — Improper Input ValidationCWE-119 — Improper Restriction of Operations within the Bounds of a Memory Buffer8 documents8 sources
Severity
8.8HIGHNVD
EPSS
3.9%
top 11.72%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
8
Google ChromeChromiumDebian Linux+5 more
Timeline
PublishedFeb 11
Latest updateMay 24

Description

Insufficient data validation in streams in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

CVSS vector

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

Affected Packages7 packages

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

Also affects: Debian Linux 10.0, 9.0, Fedora 30, 31

Patches

Patch: crbug.com ↗Patch: crbug.com ↗

🔴Vulnerability Details

3
GHSA
GHSA-4x5q-5p8j-63qv: Insufficient data validation in streams in Google Chrome prior to 80↗2022-05-24
▶
CVEList
CVE-2020-6416: Insufficient data validation in streams in Google Chrome prior to 80↗2020-02-11
▶
OSV
CVE-2020-6416: Insufficient data validation in streams in Google Chrome prior to 80↗2020-02-11
▶

📋Vendor Advisories

3
Red Hat
chromium-browser: Insufficient data validation in streams↗2020-02-04
▶
Chrome
Stable Channel Update for Desktop: CVE-2020-6415↗2020-02-04
▶
Debian
CVE-2020-6416: chromium - Insufficient data validation in streams in Google Chrome prior to 80.0.3987.87 a...↗2020
▶

💬Community

1
Bugzilla
CVE-2020-6416 chromium-browser: Insufficient data validation in streams↗2020-02-10
▶
CVE-2020-6416 — Improper Input Validation in Google | cvebase