Heap corruption via crafted HTML
Published Feb 11, 2020 · Updated Aug 4, 2024
Heap corruption in Blink in Google Chrome before 80.0.3987.87 allows remote attackers to corrupt browser memory via crafted HTML. Google has not published the affected Blink code path or the incorrect operation that corrupts heap memory. User interaction is required to open the crafted page; the disclosed consequence is heap corruption, with no narrower outcome documented.
Summary
What happened
Heap corruption in Blink in Google Chrome before 80.0.3987.87 allows remote attackers to corrupt browser memory via crafted HTML. Google has not published the affected Blink code path or the incorrect operation that corrupts heap memory. User interaction is required to open the crafted page; the disclosed consequence is heap corruption, with no narrower outcome documented.
The record
- CVE
- CVE-2020-6404
- Published
- Feb 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 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.87
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