Memory corruption via V8 out-of-bounds write
Published Nov 1, 2022 · Updated May 5, 2025
Out-of-bounds write in V8 in Google Chrome before 106.0.5249.91 allows remote attackers to corrupt memory through a crafted HTML page. Google identifies V8 as the locus but does not disclose the specific routine or validation failure that permits a write beyond allocated memory. A user must open attacker-controlled HTML; public materials do not state whether the resulting corruption causes a crash or code execution.
Summary
What happened
Out-of-bounds write in V8 in Google Chrome before 106.0.5249.91 allows remote attackers to corrupt memory through a crafted HTML page. Google identifies V8 as the locus but does not disclose the specific routine or validation failure that permits a write beyond allocated memory. A user must open attacker-controlled HTML; public materials do not state whether the resulting corruption causes a crash or code execution.
The record
- CVE
- CVE-2022-3373
- Published
- Nov 1, 2022
- Updated
- May 5, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record 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 <106.0.5249.91
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