ChromeWeb browser · Google
CVE-2022-4193
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficient policy enforcement in File System API in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to bypass file system restrictions via a crafted HTML page. (Chromium security severity: Medium)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA vulnerability in Google Chrome's File System API prior to version 108.0.5359.71 allows a remote attacker to bypass file system restrictions through a crafted HTML page. This enables unauthorized access to the local file system from a web context, violating the security boundary between web content and local files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 108.0.5359.71CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome is installedCheck for Chrome on the system: Windows - look in C:\Program Files\Google\Chrome\Application\ or via registry; macOS - check /Applications/Chrome.app; Linux - check /opt/google/chrome/ or via package manager (dpkg -l | grep chrome, rpm -q google-chrome)Affected if Google Chrome is present on the endpoint
-
Determine installed Chrome versionOpen Chrome and navigate to chrome://settings/help, or run 'chrome --version' from command line, or right-click chrome.exe and select Properties > Details to view File VersionAffected if Version cannot be determined or returns a value less than 108.0.5359.71
-
Compare version against vulnerable rangeCompare the identified version number to the affected threshold: any version below 108.0.5359.71 falls within the vulnerable rangeAffected if Installed version is lower than 108.0.5359.71
The environment is affected if Google Chrome is installed with a version below 108.0.5359.71
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped108.0.5359.71
Update Google Chrome to version 108.0.5359.71 or later. Organizations should deploy the update via standard patch management processes and verify completion across managed endpoints.
108.0.5359.71 or later
- Open Google Chrome browser
- Navigate to Settings > Help > About Google Chrome
- Chrome will automatically check for updates
- If version is below 108.0.5359.71, click 'Update Google Chrome' to download and install the fix
- Restart the browser to complete the update
- Alternatively, download the latest Chrome version from chrome.google.com
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4193 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-4193 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data