CVE-2024-7971highunder attackCWE-843

CVE-2024-7971: high-severity vulnerability in Google Chrome

Published · Updated

78Vexday Risk Score

Prioritize patching. It under exploitation confirmed by CISA and has a public proof of concept.

ssvc Actcvss 8.8epss 21%
from disclosure to weapon234 days
Published on NVDAug 21
1st PoC+234d
CISA KEV+5d
exploitation probability
21%top 2% of all CVEs
observed exploitation
yesCISA + VulnCheck
3 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.

Not affected
1 product — because the vulnerable code is not present in the product
red_hat_products
Action required by CISAfederal deadline: 2024-09-16

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

In short

A flaw in Chrome's V8 JavaScript engine allows attackers to confuse data types, leading to memory corruption. An attacker can craft a malicious webpage that exploits this to crash your browser or potentially run harmful code.

Technical detail

Type confusion vulnerability in V8 engine permits remote code execution through heap corruption when processing crafted HTML. Attack vector is network-based (malicious webpage), requiring only user interaction to visit the page; no authentication or special privileges needed. Impact includes arbitrary code execution in the browser's security context.

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 128.0.6613.84 allowed a remote attacker to exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected products
Google · Chrome
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.