Skip to content
Fencer Vulns
high 8.8

CVE-2020-6453 json

Inappropriate implementation in V8 in Google Chrome prior to 80.0.3987.162 allowed a remote attacker to potentially exploit heap corruption…

published 2020-06-03 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-27603

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits
0
none known

Summary

Inappropriate implementation in V8 in Google Chrome prior to 80.0.3987.162 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Patch / fix

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

debian advisories DEBIAN-CVE-2020-6453

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

ubuntu advisories UBUNTU-CVE-2020-6453

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

red hat advisories RHSA-2020:1350

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-6453 updated cvss 8.8

chromium-browser: Inappropriate implementation in V8

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

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. 0-day patched (Project Zero)
  3. Published

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-03-26
Patched
2020-03-31
Details
project zero tracker

Exploit prediction

0.91% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).

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
Technology feeds

References

Sources

Fencer Vulns 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.