Heap corruption via V8 use-after-free
Published Nov 9, 2022 · Updated Oct 23, 2024
Use-after-free in V8 in Google Chrome before 107.0.5304.106 allows remote attackers to exploit heap corruption via a crafted HTML page. Google has not disclosed the affected V8 object or the stale-lifetime operation that causes memory to be reused after it is freed. The attack requires a user to load the crafted page; the published record does not establish code execution or a sandbox escape.
Summary
What happened
Use-after-free in V8 in Google Chrome before 107.0.5304.106 allows remote attackers to exploit heap corruption via a crafted HTML page. Google has not disclosed the affected V8 object or the stale-lifetime operation that causes memory to be reused after it is freed. The attack requires a user to load the crafted page; the published record does not establish code execution or a sandbox escape.
The record
- CVE
- CVE-2022-3885
- Published
- Nov 9, 2022
- Updated
- Oct 23, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, 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.
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