CVE-2020-6404 json
Inappropriate implementation in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially exploit heap corrupti…
published 6y ago modified 4mo ago also EUVD-2020-27554
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
Inappropriate implementation in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Patch / fix
- Google Chrome 80.0.3987.87
- chromium Debian 14, Debian 13, Debian 12 80.0.3987.106-1
debian advisories DEBIAN-CVE-2020-6404
- chromium-browser Ubuntu 16.04 LTS 80.0.3987.87-0ubuntu0.16.04.1
- chromium-browser Ubuntu 18.04 LTS 80.0.3987.87-0ubuntu0.18.04.1
ubuntu advisories UBUNTU-CVE-2020-6404
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- chromium-browser RHEL 6 EXTRAS 80.0.3987.87-1.el6_10
red hat advisories RHSA-2020:0514
- chromium openSUSE Tumbleweed 93.0.4577.82-1.1
- chromium openSUSE Tumbleweed 113.0.5672.92-1.1
- re2 Package Hub 12 SP3, Package Hub 12 20200101-25.1
- chromium Package Hub 12 SP3, Package Hub 12 80.0.3987.87-31.1
- chromium Package Hub 15 SP1 80.0.3987.87-bp151.3.59.1
- chromium openSUSE Leap 15.1 80.0.3987.87-lp151.2.63.1
opensuse advisories openSUSE-SU-2024:10681-1openSUSE-SU-2024:12948-1openSUSE-SU-2020:0233-1openSUSE-SU-2020:0210-1openSUSE-SU-2020:0189-1
- chromium Arch Linux 80.0.3987.87-1
arch linux advisories AVG-1092
- crbug.com/1024256 advisory
Is CVE-2020-6404 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-6404 updated cvss 8.8
chromium-browser: Inappropriate implementation in Blink
-
Red Hat Enterprise Linux Desktop Supplementary (v. 6) chromium-browser 80.0.3987.87-1.el6_10 Red Hat Enterprise Linux HPC Node Supplementary (v. 6) chromium-browser 80.0.3987.87-1.el6_10 Red Hat Enterprise Linux Server Supplementary (v. 6) chromium-browser 80.0.3987.87-1.el6_10 Red Hat Enterprise Linux Workstation Supplementary (v. 6) chromium-browser 80.0.3987.87-1.el6_10fixed: vendor fix RHSA-2020:0514
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.05% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- crbug.com https://crbug.com/1024256 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
- Technology feeds
References
-
crbug.com
/1024256
exploit, issue-tracking, patch, vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2020-02/msg00015.html
vendor-advisory, third-party-advisory
-
access.redhat.com
/errata/RHSA-2020:0514
vendor-advisory, third-party-advisory
-
lists.opensuse.org
/opensuse-security-announce/2020-02/msg00025.html
vendor-advisory, mailing-list, third-party-advisory
-
debian.org
/security/2020/dsa-4638
vendor-advisory, third-party-advisory
-
security.gentoo.org
/glsa/202003-08
vendor-advisory, third-party-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/6IOHSO6BUKC6I66J5PZOMAGFVJ66ZS57/
vendor-advisory
-
chromereleases.googleblog.com
/2020/02/stable-channel-update-for-desktop.html
vendor-advisory
Sources
- CVE List CVE-2020-6404
- NVD CVE-2020-6404
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.