Heap corruption via V8 type confusion
Published Nov 19, 2024 · Updated Nov 21, 2024
Type confusion in V8 in Google Chrome before 131.0.6778.85 allows remote attackers to corrupt heap memory via a crafted HTML page. Google identifies V8 as the affected component but keeps the underlying bug record restricted, so the specific object-type mismatch and code locus are undisclosed. Exploitation requires a user to load attacker-controlled HTML; successful heap corruption can compromise the Chrome process's confidentiality, integrity, and availability.
Summary
What happened
Type confusion in V8 in Google Chrome before 131.0.6778.85 allows remote attackers to corrupt heap memory via a crafted HTML page. Google identifies V8 as the affected component but keeps the underlying bug record restricted, so the specific object-type mismatch and code locus are undisclosed. Exploitation requires a user to load attacker-controlled HTML; successful heap corruption can compromise the Chrome process's confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-11395
- Published
- Nov 19, 2024
- Updated
- Nov 21, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 19, 2024CVE publishedPublication date reported by the CVE source.
- Nov 21, 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=0 <131.0.6778.85
- Affected versionversion=131.0.6778.85 <131.0.6778.85
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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