CVE-2024-3159
Published: 06 April 2024
Summary
CVE-2024-3159 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked in the top 9.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2024-3159 is an out-of-bounds memory access vulnerability in the V8 JavaScript engine within Google Chrome versions prior to 123.0.6312.105. The flaw, tracked under CWE-119 and CWE-125, permits unauthorized memory operations and carries a CVSS 3.1 base score of 8.8 reflecting network attack vector, low complexity, and high impact on confidentiality, integrity, and availability.
A remote attacker can exploit the issue by convincing a target user to visit a specially crafted HTML page, after which arbitrary read and write primitives become available in the renderer process. No authentication or special privileges are required beyond standard user interaction with a web page.
Chrome stable channel updates released on 2024-04-06 upgraded the affected component to version 123.0.6312.105, closing the vulnerability; downstream distributions such as Fedora have issued corresponding package updates that pull in the same fix.
EPSS scores have remained low, with a current value of 0.0568 and a peak of 0.0639, indicating limited observed exploitation interest to date.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-31756
Vulnerability details
Out of bounds memory access in V8 in Google Chrome prior to 123.0.6312.105 allowed a remote attacker to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: High)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Out-of-bounds memory access in Chrome's V8 JavaScript engine enables remote arbitrary read/write via crafted HTML, facilitating drive-by compromise (T1189) and exploitation for client execution (T1203).
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Ongoing control assessments and code testing (static/dynamic analysis, fuzzing) surface memory buffer restriction failures, which are then remediated before release.
Managed runtimes used by platform-independent applications (e.g., JVM, CLR) enforce memory safety, preventing most buffer overflows that require direct memory manipulation.
Memory protections (e.g., W^X, ASLR) make exploitation of buffer-boundary violations far harder to turn into code execution.
Detects exploitation attempts that produce memory corruption, crashes, or anomalous behavior.