CVE-2020-6418highunder attackCWE-843

CVE-2020-6418: high-severity vulnerability in Google Chrome

Published · Updated

100Vexday Risk Score

Patch now. It under exploitation confirmed by CISA and has a working public exploit.

ssvc Actcvss 8.8epss 79%
from disclosure to weapon0 days
Published on NVDFeb 27
1st PoCFeb 27
metasploitFeb 19
CISA KEV+615d
exploitation probability
79%top 1% of all CVEs
observed exploitation
yesCISA + VulnCheck
11 public exploit(s)
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Red HatVEX document ↗
Fixed
4 products (14 components)
Red Hat Enterprise Linux Desktop Supplementary (v. 6) · Red Hat Enterprise Linux Server Supplementary (v. 6) · Red Hat Enterprise Linux Workstation Supplementary (v. 6) · Red Hat Enterprise Linux HPC Node Supplementary (v. 6)
fix ↗
Action required by CISAfederal deadline: 2022-05-03

Apply updates per vendor instructions.

In short

Google Chrome's JavaScript engine (V8) had a flaw where it confused different data types, allowing attackers to corrupt computer memory through a malicious webpage. This could lead to crashes or arbitrary code execution.

Technical detail

Type confusion vulnerability in V8 allows remote attackers to trigger heap corruption by crafting malicious HTML pages that exploit incorrect type handling during JavaScript execution. Exploitation requires user interaction to visit a crafted page; successful exploitation can result in arbitrary code execution with browser privileges.

Summary generated and translated by AI from the official description.

The full analysis of this CVE is available in Portuguese →

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/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected products
Google · Chrome
public PoCs found — 11✓ VexDay Proof
exploitdb✓ VexDay Proofwww.exploit-db.com/exploits/48186githubgithub.com/Goyotan/CVE-2020-6418-PoC★ 3githubgithub.com/ulexec/ChromeSHELFLoader★ 3githubgithub.com/SivaPriyaRanganatha/CVE-2020-6418★ 1githubgithub.com/a-mansilla/CVE-2020-6418★ 0githubgithub.com/ASkyeye/CVE-2020-6418★ 0vulncheckvulncheck.com/xdb/f153146b6e74unverifiedvulncheckvulncheck.com/xdb/09aef40e5781unverifiedvulncheckvulncheck.com/xdb/68df06773b3bunverifiedcve_referencepacketstormsecurity.com/files/156632/Google-Chrome-80-JSCreate-Side-Effect-Type-Confusion.htmlunverifiedvulncheckvulncheck.com/xdb/b18325613fe1unverified
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — Google Chrome

In the same product, most dangerous first.

CVE-2023-4863HIGHCVE-2023-4863EPSS 100.0%KEVCVE-2018-17463HIGHCVE-2018-17463EPSS 84.6%KEVCVE-2021-21224HIGHCVE-2021-21224EPSS 84.2%KEVCVE-2022-2294HIGHCVE-2022-2294EPSS 70.5%KEVCVE-2021-21220HIGHCVE-2021-21220EPSS 70.4%KEVCVE-2021-30551HIGHCVE-2021-30551EPSS 64.7%KEV
References
http://packetstormsecurity.com/files/156632/Google-Chrome-80-JSCreate-Side-Effect-Type-Confusion.htmlhttps://access.redhat.com/errata/RHSA-2020:0738https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop_24.htmlhttps://crbug.com/1053604https://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-08https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-6418https://www.debian.org/security/2020/dsa-4638