CVE-2022-0337: Inappropriate implementation in File System API
Inappropriate implementation in File System API in Google Chrome on Windows prior to 97.0.4692.71 allowed a remote attacker to obtain potentially sensitive information via a crafted HTML page. (Chrome security severity: High)
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Google Chrome (Trace Event)to a version that resolves this vulnerability.Fixed in 97.0.4692.71
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-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-0115
- 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-0337?
CVE-2022-0337 is classified as a High severity vulnerability.
How do I fix CVE-2022-0337?
To fix CVE-2022-0337, update Google Chrome to version 97.0.4692.71 or later.
What type of information can be exposed by CVE-2022-0337?
CVE-2022-0337 may allow a remote attacker to obtain potentially sensitive information through a crafted HTML page.
Which versions of Google Chrome are affected by CVE-2022-0337?
Google Chrome versions prior to 97.0.4692.71 are affected by CVE-2022-0337.
Is CVE-2022-0337 specific to any operating system?
CVE-2022-0337 specifically affects Google Chrome running on Windows.