Out-of-bounds memory access via uninitialized File API resource
Published Feb 11, 2022 · Updated Aug 2, 2024
Uninitialized resource use in Google Chrome before 97.0.4692.71 allows remote attackers to access out-of-bounds memory via crafted HTML. The public record identifies the File API as the affected locus but does not disclose which resource is consumed before initialization or the exact invalid memory operation. A user must load attacker-controlled HTML; the documented result is out-of-bounds memory access, while code execution or a specific read or write primitive is not established.
Summary
What happened
Uninitialized resource use in Google Chrome before 97.0.4692.71 allows remote attackers to access out-of-bounds memory via crafted HTML. The public record identifies the File API as the affected locus but does not disclose which resource is consumed before initialization or the exact invalid memory operation. A user must load attacker-controlled HTML; the documented result is out-of-bounds memory access, while code execution or a specific read or write primitive is not established.
The record
- CVE
- CVE-2022-0115
- Published
- Feb 11, 2022
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-908, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 <97.0.4692.71
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