Heap corruption via out-of-bounds stream access
Published Feb 27, 2020 · Updated Aug 4, 2024
Out-of-bounds memory access in Google Chrome before 80.0.3987.122 allows remote attackers to corrupt heap memory via crafted HTML. The public Chrome record identifies the streams component but does not disclose the faulty operation or memory boundary. Exploitation requires a user to open attacker-controlled HTML; the published record establishes potentially exploitable heap corruption.
Summary
What happened
Out-of-bounds memory access in Google Chrome before 80.0.3987.122 allows remote attackers to corrupt heap memory via crafted HTML. The public Chrome record identifies the streams component but does not disclose the faulty operation or memory boundary. Exploitation requires a user to open attacker-controlled HTML; the published record establishes potentially exploitable heap corruption.
The record
- CVE
- CVE-2020-6407
- Published
- Feb 27, 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 27, 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.122
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