Heap corruption via V8 type confusion
Published Oct 8, 2024 · Updated Oct 9, 2024
Type confusion in V8 in Google Chrome before 129.0.6668.100 allows remote attackers to trigger heap corruption through a crafted HTML page. Google has not published which V8 operation confuses object types or how the crafted page corrupts the heap. Exploitation requires a user to load attacker-controlled HTML; the published record does not specify the resulting code-execution or crash impact.
Summary
What happened
Type confusion in V8 in Google Chrome before 129.0.6668.100 allows remote attackers to trigger heap corruption through a crafted HTML page. Google has not published which V8 operation confuses object types or how the crafted page corrupts the heap. Exploitation requires a user to load attacker-controlled HTML; the published record does not specify the resulting code-execution or crash impact.
The record
- CVE
- CVE-2024-9603
- Published
- Oct 8, 2024
- Updated
- Oct 9, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 8, 2024CVE publishedPublication date reported by the CVE source.
- Oct 9, 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.100
- Affected versionversion=129.0.6668.100 <129.0.6668.100
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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