Heap corruption via V8 type confusion
Published Nov 9, 2022 · Updated Oct 23, 2024
Type confusion in V8 in Google Chrome before 107.0.5304.106 allows remote attackers to corrupt heap memory via a crafted HTML page. Google identifies the affected locus only as V8 and has not published which operation applies an incompatible type to attacker-controlled data. Exploitation requires a user to load the crafted page; the published record bounds the result to heap corruption rather than confirming code execution.
Summary
What happened
Type confusion in V8 in Google Chrome before 107.0.5304.106 allows remote attackers to corrupt heap memory via a crafted HTML page. Google identifies the affected locus only as V8 and has not published which operation applies an incompatible type to attacker-controlled data. Exploitation requires a user to load the crafted page; the published record bounds the result to heap corruption rather than confirming code execution.
The record
- CVE
- CVE-2022-3889
- Published
- Nov 9, 2022
- Updated
- Oct 23, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 9, 2022CVE publishedPublication date reported by the CVE source.
- Oct 23, 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=0 <107.0.5304.106
- Affected versionversion=unspecified <107.0.5304.106
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