Renderer heap corruption via stale WebAudio context
Published Apr 13, 2020 · Updated Aug 4, 2024
Use after free in WebAudio in Google Chrome before 80.0.3987.162 allows remote attackers to corrupt renderer heap memory via a crafted HTML page. An AudioHandler retained a garbage-collected BaseAudioContext and dereferenced it from a queued callback before destructor cleanup removed the stale relationship. A user must load the crafted page; exploitation remains inside the renderer sandbox unless combined with another flaw.
Summary
What happened
Use after free in WebAudio in Google Chrome before 80.0.3987.162 allows remote attackers to corrupt renderer heap memory via a crafted HTML page. An AudioHandler retained a garbage-collected BaseAudioContext and dereferenced it from a queued callback before destructor cleanup removed the stale relationship. A user must load the crafted page; exploitation remains inside the renderer sandbox unless combined with another flaw.
The record
- CVE
- CVE-2020-6450
- Published
- Apr 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 13, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=unspecified <80.0.3987.162
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
- WebAudio stale BaseAudioContext reproducerproof of concept · demonstrated
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