Heap corruption via DevTools use-after-free
Published Jul 16, 2024 · Updated Mar 13, 2025
Use-after-free in DevTools in Google Chrome before 122.0.6261.57 allows remote attackers to trigger heap corruption via crafted HTML. Google has not published the affected DevTools object or the lifetime-management error that leaves freed memory accessible. A user must open the crafted page; successful exploitation corrupts browser-process memory, but the exact post-corruption outcome is undisclosed.
Summary
What happened
Use-after-free in DevTools in Google Chrome before 122.0.6261.57 allows remote attackers to trigger heap corruption via crafted HTML. Google has not published the affected DevTools object or the lifetime-management error that leaves freed memory accessible. A user must open the crafted page; successful exploitation corrupts browser-process memory, but the exact post-corruption outcome is undisclosed.
The record
- CVE
- CVE-2024-3168
- Published
- Jul 16, 2024
- Updated
- Mar 13, 2025
- 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.
- Mar 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 <122.0.6261.57
- Affected versionversion=122.0.6261.57 <122.0.6261.57
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