Arbitrary read and write via V8 type confusion
Published May 22, 2024 · Updated Feb 13, 2025
Type confusion in V8 in Google Chrome before 125.0.6422.76 allows remote attackers to perform arbitrary reads and writes via crafted HTML. Google has not published the affected V8 routine or the incompatible type transition that causes the memory access. Exploitation requires a user to open the crafted page; public sources do not establish code execution or a sandbox escape.
Summary
What happened
Type confusion in V8 in Google Chrome before 125.0.6422.76 allows remote attackers to perform arbitrary reads and writes via crafted HTML. Google has not published the affected V8 routine or the incompatible type transition that causes the memory access. Exploitation requires a user to open the crafted page; public sources do not establish code execution or a sandbox escape.
The record
- CVE
- CVE-2024-5158
- Published
- May 22, 2024
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=0 <125.0.6422.76
- Affected versionversion=125.0.6422.76 <125.0.6422.76
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