Heap corruption via V8 type confusion
Published Apr 30, 2021 · Updated Aug 3, 2024
Type confusion in V8 in Google Chrome before 90.0.4430.93 allows remote attackers to trigger heap corruption via crafted HTML. Google identifies V8 as the affected component but has not published the incompatible type operation or code locus that mishandles page content. User interaction is required to load attacker-controlled HTML, and the documented consequence is heap corruption rather than a sandbox escape.
Summary
What happened
Type confusion in V8 in Google Chrome before 90.0.4430.93 allows remote attackers to trigger heap corruption via crafted HTML. Google identifies V8 as the affected component but has not published the incompatible type operation or code locus that mishandles page content. User interaction is required to load attacker-controlled HTML, and the documented consequence is heap corruption rather than a sandbox escape.
The record
- CVE
- CVE-2021-21230
- Published
- Apr 30, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 30, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <90.0.4430.93
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