Browser memory corruption via crafted HTML
Published Apr 17, 2024 · Updated Mar 14, 2025
Object corruption in V8 in Google Chrome before 124.0.6367.60 allows remote attackers to corrupt browser objects via crafted HTML. The public Chrome and Chromium records identify V8 as the locus but do not disclose the faulty operation that mishandles the page. Exploitation requires user interaction with attacker-controlled content and can compromise browser-process confidentiality, integrity, and availability.
Summary
What happened
Object corruption in V8 in Google Chrome before 124.0.6367.60 allows remote attackers to corrupt browser objects via crafted HTML. The public Chrome and Chromium records identify V8 as the locus but do not disclose the faulty operation that mishandles the page. Exploitation requires user interaction with attacker-controlled content and can compromise browser-process confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-3832
- Published
- Apr 17, 2024
- Updated
- Mar 14, 2025
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-119, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2024CVE publishedPublication date reported by the CVE source.
- Mar 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=38
- Affected versionversion=39
- Affected versionversion=40
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Chromium issue 331358160proof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo