CVE-2022-0115: Uninitialized Use in File API
Uninitialized use in File API in Google Chrome prior to 97.0.4692.71 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.
Credit
Affected Software
Remediation
Patch Available
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2022-0096
- CVE-2022-0097
- CVE-2022-0098
- CVE-2022-0099
- CVE-2022-0100
- CVE-2022-0101
- CVE-2022-0337
- CVE-2022-0102
- CVE-2022-0103
- CVE-2022-4924
- CVE-2022-0104
- CVE-2022-0105
- CVE-2022-0106
- CVE-2022-0107
- CVE-2022-0108
- CVE-2022-0109
- CVE-2022-0110
- CVE-2022-0111
- CVE-2022-0112
- CVE-2022-0113
- CVE-2022-0114
- CVE-2022-0116
- CVE-2022-0117
- CVE-2022-0118
- CVE-2022-0120
- CVE-2022-4925
Frequently Asked Questions
What is the severity of CVE-2022-0115?
CVE-2022-0115 has been classified as a high severity vulnerability due to the potential for out of bounds memory access.
How do I fix CVE-2022-0115?
To fix CVE-2022-0115, ensure that your Google Chrome or Chromium browser is updated to version 97.0.4692.71 or later.
What versions are affected by CVE-2022-0115?
CVE-2022-0115 affects Google Chrome versions prior to 97.0.4692.71 and various versions of Chromium on Debian systems.
Can CVE-2022-0115 be exploited remotely?
Yes, CVE-2022-0115 can be exploited remotely via a specially crafted HTML page.
Is there a workaround for CVE-2022-0115?
There are no specific workarounds for CVE-2022-0115, the best mitigation is to upgrade to the safe version.