Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2022-0337: Information Disclosure in Chrome File System API

Published Jan 2, 2023 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3.1
EPSS1.4%73rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Google
IdentifiersCVE-2022-0337CWE-200

CVE-2022-0337 is an information disclosure vulnerability in the File System API implementation in Google Chrome on Windows, prior to version 97.0.4692.71. The vulnerability arises from an inappropriate implementation that allows a remote attacker to craft an HTML page capable of accessing potentially sensitive information from the victim's system via the browser's File System API.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote attacker can exploit this vulnerability by luring a user to visit a malicious HTML page, which can then access and exfiltrate sensitive information from the user's system through the File System API. This could lead to exposure of confidential files or data stored on the user's machine.

Mitigation

If you can’t patch tonight, do this now.

As a temporary mitigation, users can disable or restrict access to the File System API via browser settings or group policy, and avoid visiting untrusted or suspicious websites until the browser is updated.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 97.0.4692.71 or later, where the vulnerability has been addressed by correcting the implementation of the File System API.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication
FAQ

Frequently asked questions

Is CVE-2022-0337 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2022-0337 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2022-0337?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2022-0337, the earliest disclosed Mar 19, 2022.
Is there a patch for CVE-2022-0337?
Upgrade Google Chrome to version 97.0.4692.71 or later, where the vulnerability has been addressed by correcting the implementation of the File System API.
What products are affected by CVE-2022-0337?
Google Chrome.
How severe is CVE-2022-0337?
CVE-2022-0337 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 1.4% (73rd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.