Heap corruption via V8 type confusion
Published Jul 28, 2022 · Updated Aug 3, 2024
Type confusion in V8 in Google Chrome before 103.0.5060.114 allows remote attackers to trigger heap corruption via a crafted HTML page. Google identifies the affected locus as V8 but has not published the mismatched runtime types or operation that corrupts the heap. A user must load attacker-controlled HTML; exploitation occurs within the browser renderer sandbox, and no sandbox escape is established for this flaw.
Summary
What happened
Type confusion in V8 in Google Chrome before 103.0.5060.114 allows remote attackers to trigger heap corruption via a crafted HTML page. Google identifies the affected locus as V8 but has not published the mismatched runtime types or operation that corrupts the heap. A user must load attacker-controlled HTML; exploitation occurs within the browser renderer sandbox, and no sandbox escape is established for this flaw.
The record
- CVE
- CVE-2022-2295
- Published
- Jul 28, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-843, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2022CVE 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 <103.0.5060.114
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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