CVE-2020-6418
Google Chromium V8 Type Confusion
- Published27 Feb 2020
- Added to CISA KEV3 Nov 2021
- Remediation due3 May 2022
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- http://packetstormsecurity.com/files/156632/Google-Chrome-80-JSCreate-Side-Effect-Type-Confusion.html
- https://access.redhat.com/errata/RHSA-2020:0738
- https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop_24.html
- https://crbug.com/1053604
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6IOHSO6BUKC6I66J5PZOMAGFVJ66ZS57/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X3B5RWJQD5LA45MYLLR55KZJOJ5NVZGP/
- https://security.gentoo.org/glsa/202003-08
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-6418
- https://www.debian.org/security/2020/dsa-4638
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2020-6418 being actively exploited?
Yes. CVE-2020-6418 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 3 Nov 2021.
How severe is CVE-2020-6418?
CVE-2020-6418 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 78.8% probability of exploitation.
Which products are affected by CVE-2020-6418?
Affected products include Google Chrome, Debian Linux, Fedoraproject Fedora, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, and 1 more.
How do I fix CVE-2020-6418?
Upgrade affected software to a fixed version, for example Google Chrome 80.0.3987.122 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2020-6418 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.