Heap corruption via Web Audio use-after-free
Published Jan 23, 2024 · Updated Jun 20, 2025
Use-after-free in Web Audio in Google Chrome before 121.0.6167.85 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies Web Audio as the affected component but has not published the object-lifetime error or code-level locus. A user must load the attacker-controlled page, and the public record does not establish whether successful corruption causes a crash or code execution.
Summary
What happened
Use-after-free in Web Audio in Google Chrome before 121.0.6167.85 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies Web Audio as the affected component but has not published the object-lifetime error or code-level locus. A user must load the attacker-controlled page, and the public record does not establish whether successful corruption causes a crash or code execution.
The record
- CVE
- CVE-2024-0807
- Published
- Jan 23, 2024
- Updated
- Jun 20, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 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=121.0.6167.85 <121.0.6167.85
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