Heap corruption via malformed V8 API input
Published Aug 21, 2024 · Updated Mar 19, 2025
Insufficient data validation in Google Chrome's V8 API before 128.0.6613.84 allows remote attackers to corrupt heap memory via a crafted extension. The public record identifies only the V8 API and does not disclose which entry point accepts invalid extension-controlled data or which validation is missing. Reaching the flaw requires a crafted Chrome extension to invoke that API, and published sources establish no consequence beyond heap corruption.
Summary
What happened
Insufficient data validation in Google Chrome's V8 API before 128.0.6613.84 allows remote attackers to corrupt heap memory via a crafted extension. The public record identifies only the V8 API and does not disclose which entry point accepts invalid extension-controlled data or which validation is missing. Reaching the flaw requires a crafted Chrome extension to invoke that API, and published sources establish no consequence beyond heap corruption.
The record
- CVE
- CVE-2024-7974
- Published
- Aug 21, 2024
- Updated
- Mar 19, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-20, T1203
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 21, 2024CVE publishedPublication date reported by the CVE source.
- Mar 19, 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=128.0.6613.84 <128.0.6613.84
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.
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