Heap corruption via V8 type confusion
Published Nov 23, 2021 · Updated Aug 4, 2024
Type confusion in V8 in Google Chrome before 95.0.4638.69 allows remote attackers to exploit heap corruption via crafted HTML. V8's type handling confuses JavaScript object representations when processing attacker-controlled page content, enabling memory corruption. Exploitation requires a user to load the malicious page; the record establishes heap corruption but does not specify a further impact.
Summary
What happened
Type confusion in V8 in Google Chrome before 95.0.4638.69 allows remote attackers to exploit heap corruption via crafted HTML. V8's type handling confuses JavaScript object representations when processing attacker-controlled page content, enabling memory corruption. Exploitation requires a user to load the malicious page; the record establishes heap corruption but does not specify a further impact.
The record
- CVE
- CVE-2021-38001
- Published
- Nov 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 23, 2021CVE 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 <95.0.4638.69
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