Heap corruption via V8 type confusion
Published May 16, 2023 · Updated May 5, 2025
Type confusion in Google Chrome before 113.0.5672.126 allows remote attackers to corrupt the heap through a crafted HTML page. Google identifies V8 as the affected component but has not disclosed the precise code locus or incompatible-type access that causes the corruption. A user must load attacker-controlled HTML; public records establish no narrower post-corruption outcome.
Summary
What happened
Type confusion in Google Chrome before 113.0.5672.126 allows remote attackers to corrupt the heap through a crafted HTML page. Google identifies V8 as the affected component but has not disclosed the precise code locus or incompatible-type access that causes the corruption. A user must load attacker-controlled HTML; public records establish no narrower post-corruption outcome.
The record
- CVE
- CVE-2023-2724
- Published
- May 16, 2023
- Updated
- May 5, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 16, 2023CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record 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=113.0.5672.126 <113.0.5672.126
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