Heap corruption via Blink type confusion
Published May 21, 2020 · Updated Aug 4, 2024
Type confusion in Blink in Google Chrome before 81.0.4044.138 allows remote attackers to trigger heap corruption via a crafted HTML page. Google identifies the affected engine and corruption result but does not publicly disclose the mismatched object types or erroneous operation. The user must load attacker-controlled HTML; the published record does not specify the post-corruption result.
Summary
What happened
Type confusion in Blink in Google Chrome before 81.0.4044.138 allows remote attackers to trigger heap corruption via a crafted HTML page. Google identifies the affected engine and corruption result but does not publicly disclose the mismatched object types or erroneous operation. The user must load attacker-controlled HTML; the published record does not specify the post-corruption result.
The record
- CVE
- CVE-2020-6464
- Published
- May 21, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, CWE-787, T1189, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 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 <81.0.4044.138
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.
Weakness, pattern, technique
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