Skip to content
Fencer Intel
high 8.8

CVE-2020-6418 kev in the critical feed json

Type confusion in V8 in Google Chrome prior to 80.0.3987.122 allowed a remote attacker to potentially exploit heap corruption via a crafted…

published 6y ago modified 4mo ago also EUVD-2020-27568

cvss
8.8
version 3.1, CNA
cisa kev
Exploited
added 2021-11-03
epss
78.8%
EPSS 78.8% chance of exploitation in 30 days, percentile 99.5%
public exploits
2
Metasploit and Exploit-DB

Summary

Type confusion in V8 in Google Chrome prior to 80.0.3987.122 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Patch / fix

cisa required action Apply updates per vendor instructions.

  • Google Chrome 80.0.3987.122
  • chromium Debian 14, Debian 13, Debian 12 80.0.3987.122-1

debian advisories DEBIAN-CVE-2020-6418

  • chromium-browser Ubuntu 16.04 LTS 80.0.3987.149-0ubuntu0.16.04.1
  • chromium-browser Ubuntu 18.04 LTS 80.0.3987.149-0ubuntu0.18.04.1

ubuntu advisories UBUNTU-CVE-2020-6418

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.122-1.el6_10

red hat advisories RHSA-2020:0738

  • chromium openSUSE Tumbleweed 93.0.4577.82-1.1
  • chromium openSUSE Tumbleweed 113.0.5672.92-1.1
  • chromium openSUSE Leap 15.1 80.0.3987.122-lp151.2.66.1
  • chromium Package Hub 12 SP3 80.0.3987.122-34.1

opensuse advisories openSUSE-SU-2024:10681-1openSUSE-SU-2024:12948-1openSUSE-SU-2020:0259-1openSUSE-SU-2020:0245-1

  • chromium Arch Linux 80.0.3987.122-1

arch linux advisories AVG-1102

Is CVE-2020-6418 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 Fencer

Vendor 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-6418 updated cvss 8.8

chromium-browser: Type confusion in V8

  • Red Hat Enterprise Linux Desktop Supplementary (v. 6) chromium-browser 80.0.3987.122-1.el6_10 Red Hat Enterprise Linux HPC Node Supplementary (v. 6) chromium-browser 80.0.3987.122-1.el6_10 Red Hat Enterprise Linux Server Supplementary (v. 6) chromium-browser 80.0.3987.122-1.el6_10 Red Hat Enterprise Linux Workstation Supplementary (v. 6) chromium-browser 80.0.3987.122-1.el6_10
    fixed: vendor fix RHSA-2020:0738

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

Timeline

  1. Found exploited as a 0-day (Project Zero)
  2. First public exploit (Metasploit exploit/multi/browser/chrome_jscreate_sideeffect)
  3. 0-day patched (Project Zero)
  4. Published
  5. Added to CISA KEV
  6. CISA patch deadline
  7. CISA SSVC: exploitation active

Known exploited

Added
5y ago
Patch by
2022-05-03 (4y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
Google, Chromium V8
CISA name
Google Chromium V8 Type Confusion Vulnerability

Zero-day

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Found
2020-02-18
Patched
2020-02-24
Details
project zero root cause analysis

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

78.81% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA 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-843 Access of Resource Using Incompatible Type
Technology feeds

References

Sources

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.