Heap corruption via WebAudio use-after-free
Published Aug 6, 2024 · Updated Aug 6, 2024
Use-after-free in Google Chrome's WebAudio component before 127.0.6533.99 allows remote attackers to corrupt heap memory via crafted HTML. The public record identifies stale-object access only at the WebAudio component level; the linked Chromium issue requires permission and discloses no code-level locus. A user must load attacker-controlled HTML, after which the documented outcome is heap corruption rather than guaranteed code execution.
Summary
What happened
Use-after-free in Google Chrome's WebAudio component before 127.0.6533.99 allows remote attackers to corrupt heap memory via crafted HTML. The public record identifies stale-object access only at the WebAudio component level; the linked Chromium issue requires permission and discloses no code-level locus. A user must load attacker-controlled HTML, after which the documented outcome is heap corruption rather than guaranteed code execution.
The record
- CVE
- CVE-2024-7536
- Published
- Aug 6, 2024
- Updated
- Aug 6, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2024CVE publishedPublication date reported by the CVE source.
- Aug 6, 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 <127.0.6533.99
- Affected versionversion=127.0.6533.99 <127.0.6533.99
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