Heap corruption via V8 type confusion
Published Oct 22, 2024 · Updated Oct 30, 2024
Type confusion in V8 in Google Chrome before 130.0.6723.69 allows remote attackers to trigger heap corruption via crafted HTML. Google identifies the affected locus only as V8 and has not disclosed which value is accessed under an incompatible type. Exploitation requires user interaction with attacker-controlled HTML; the documented consequence is heap corruption, not separately confirmed code execution.
Summary
What happened
Type confusion in V8 in Google Chrome before 130.0.6723.69 allows remote attackers to trigger heap corruption via crafted HTML. Google identifies the affected locus only as V8 and has not disclosed which value is accessed under an incompatible type. Exploitation requires user interaction with attacker-controlled HTML; the documented consequence is heap corruption, not separately confirmed code execution.
The record
- CVE
- CVE-2024-10230
- Published
- Oct 22, 2024
- Updated
- Oct 30, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 22, 2024CVE publishedPublication date reported by the CVE source.
- Oct 30, 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 <130.0.6723.69
- Affected versionversion=130.0.6723.69 <130.0.6723.69
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