Out-of-bounds memory access
Published Aug 21, 2024 · Updated Aug 22, 2024
Inappropriate implementation in V8 in Google Chrome before 128.0.6613.84 allows remote attackers to access memory out of bounds via crafted HTML. The public vendor notice identifies V8 as the affected locus but does not disclose which operation mishandles untrusted page content; the linked issue requires authentication. Rendering attacker-controlled HTML is the exposure gate, and the published impact is bounded to out-of-bounds memory access rather than demonstrated code execution.
Summary
What happened
Inappropriate implementation in V8 in Google Chrome before 128.0.6613.84 allows remote attackers to access memory out of bounds via crafted HTML. The public vendor notice identifies V8 as the affected locus but does not disclose which operation mishandles untrusted page content; the linked issue requires authentication. Rendering attacker-controlled HTML is the exposure gate, and the published impact is bounded to out-of-bounds memory access rather than demonstrated code execution.
The record
- CVE
- CVE-2024-7972
- Published
- Aug 21, 2024
- Updated
- Aug 22, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-119, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 22, 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 <128.0.6613.84
- 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.
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