Heap corruption via media heap buffer overflow
Published Apr 13, 2020 · Updated Aug 4, 2024
Heap buffer overflow in Chrome's media component before 80.0.3987.162 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the locus only as the media component; the affected decoder, function, and bounds-check failure remain undisclosed. Exploitation requires a user to load attacker-controlled page content, and the documented consequence is heap corruption within the browser process.
Summary
What happened
Heap buffer overflow in Chrome's media component before 80.0.3987.162 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the locus only as the media component; the affected decoder, function, and bounds-check failure remain undisclosed. Exploitation requires a user to load attacker-controlled page content, and the documented consequence is heap corruption within the browser process.
The record
- CVE
- CVE-2020-6452
- Published
- Apr 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1189
- 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
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