Heap corruption via feedback-vectorless OSR
Published Apr 13, 2020 · Updated Aug 4, 2024
Type confusion in V8 in Google Chrome before 81.0.4044.92 allows remote attackers to corrupt browser heap memory via crafted HTML. V8 can initiate on-stack replacement on a closure lacking a feedback vector because OSR state is tied to a bytecode array and survives bytecode flushing. A victim must load attacker-controlled content; published evidence establishes heap corruption but not a sandbox escape or host-code execution.
Summary
What happened
Type confusion in V8 in Google Chrome before 81.0.4044.92 allows remote attackers to corrupt browser heap memory via crafted HTML. V8 can initiate on-stack replacement on a closure lacking a feedback vector because OSR state is tied to a bytecode array and survives bytecode flushing. A victim must load attacker-controlled content; published evidence establishes heap corruption but not a sandbox escape or host-code execution.
The record
- CVE
- CVE-2020-6430
- Published
- Apr 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, 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 <81.0.4044.92
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