Heap corruption via invalid V8 deoptimization assumptions
Published Sep 17, 2024 · Updated Sep 18, 2024
Type confusion in V8 in Google Chrome before 129.0.6668.58 allows remote attackers to trigger heap corruption via crafted HTML. JSPI stack switching breaks V8's lazy-deoptimization guarantees, causing compiled code to retain incompatible type assumptions. User interaction is required to load the page; public sources do not establish whether successful corruption yields code execution or only a crash.
Summary
What happened
Type confusion in V8 in Google Chrome before 129.0.6668.58 allows remote attackers to trigger heap corruption via crafted HTML. JSPI stack switching breaks V8's lazy-deoptimization guarantees, causing compiled code to retain incompatible type assumptions. User interaction is required to load the page; public sources do not establish whether successful corruption yields code execution or only a crash.
The record
- CVE
- CVE-2024-8904
- Published
- Sep 17, 2024
- Updated
- Sep 18, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2024CVE publishedPublication date reported by the CVE source.
- Sep 18, 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 <129.0.6668.58
- Affected versionversion=129.0.6668.58 <129.0.6668.58
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