Heap corruption via V8 type confusion
Published Dec 11, 2024 · Updated Dec 17, 2024
Type confusion in V8 in Google Chrome before 131.0.6778.139 allows remote attackers to corrupt heap memory via crafted HTML. Rendering attacker-controlled HTML triggers incompatible-type access; Google has not disclosed the affected V8 code path or types. Exploitation requires a user to load the crafted page, and the public record establishes heap corruption but not a specific post-corruption outcome.
Summary
What happened
Type confusion in V8 in Google Chrome before 131.0.6778.139 allows remote attackers to corrupt heap memory via crafted HTML. Rendering attacker-controlled HTML triggers incompatible-type access; Google has not disclosed the affected V8 code path or types. Exploitation requires a user to load the crafted page, and the public record establishes heap corruption but not a specific post-corruption outcome.
The record
- CVE
- CVE-2024-12381
- Published
- Dec 11, 2024
- Updated
- Dec 17, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2024CVE publishedPublication date reported by the CVE source.
- Dec 17, 2024Record 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=131.0.6778.139 <131.0.6778.139
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
No public exploit references are available in this record.
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