Heap corruption via QUIC use-after-free
Published Apr 17, 2024 · Updated Feb 13, 2025
Use-after-free in Google Chrome's QUIC component before 124.0.6367.60 allows remote attackers to corrupt heap memory via crafted HTML. Google has not disclosed which QUIC object is freed prematurely or which subsequent operation dereferences the stale pointer. Exploitation requires prior renderer compromise; public evidence limits the demonstrated consequence to heap corruption within the browser process.
Summary
What happened
Use-after-free in Google Chrome's QUIC component before 124.0.6367.60 allows remote attackers to corrupt heap memory via crafted HTML. Google has not disclosed which QUIC object is freed prematurely or which subsequent operation dereferences the stale pointer. Exploitation requires prior renderer compromise; public evidence limits the demonstrated consequence to heap corruption within the browser process.
The record
- CVE
- CVE-2024-3837
- Published
- Apr 17, 2024
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 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=*
- Affected versionversion=124.0.6367.60 <124.0.6367.60
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