Heap corruption via V8 use after free
Published Jul 16, 2024 · Updated Aug 1, 2024
Use after free in V8 in Google Chrome before 121.0.6167.139 allows remote attackers to corrupt heap memory through a crafted HTML page. The public record identifies V8 and reuse of freed memory but does not disclose the affected routine or the lifetime error that leaves the object reachable. Exploitation requires a user to open attacker-controlled HTML, after which the corruption can compromise browser confidentiality, integrity, and availability.
Summary
What happened
Use after free in V8 in Google Chrome before 121.0.6167.139 allows remote attackers to corrupt heap memory through a crafted HTML page. The public record identifies V8 and reuse of freed memory but does not disclose the affected routine or the lifetime error that leaves the object reachable. Exploitation requires a user to open attacker-controlled HTML, after which the corruption can compromise browser confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-3169
- Published
- Jul 16, 2024
- Updated
- Aug 1, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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 <121.0.6167.139
- Affected versionversion=121.0.6167.139 <121.0.6167.139
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