CVE-2023-0140
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 · uneditedInappropriate implementation in in File System API in Google Chrome on Windows prior to 109.0.5414.74 allowed a remote attacker to bypass file system restrictions via a crafted HTML page. (Chromium security severity: Low)
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 confidenceGoogle Chrome on Windows had an inappropriate implementation in its File System API that allowed a remote attacker to bypass file system restrictions via a crafted HTML page. The vulnerability existed prior to version 109.0.5414.74.
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< 109.0.5414.74CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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.
-
Check Google Chrome version on WindowsOpen Google Chrome, click the three-dot menu in the top-right corner, select Help, then select About Google Chrome. Alternatively, open Command Prompt and run: chrome --versionAffected if The displayed version number is less than 109.0.5414.74
-
Verify Windows platformThis vulnerability affects only Google Chrome on Windows. Confirm the operating system is Windows by opening Settings > System > About or running 'systeminfo' in Command PromptAffected if The system is running Windows and the Chrome version from step 1 is below 109.0.5414.74
You are affected if Google Chrome on Windows is installed with a version lower than 109.0.5414.74
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 · scoped109.0.5414.74
Update Google Chrome to version 109.0.5414.74 or later on all Windows systems to remediate this file system restriction bypass vulnerability.
Chrome 109.0.5414.74 (Windows)
- Open Google Chrome on Windows
- Click the three-dot menu icon in the top-right corner
- Select 'Help' then 'About Google Chrome'
- Chrome will automatically check for updates and download version 109.0.5414.74 or later
- Click 'Relaunch' or restart Chrome manually to apply the update
- Verify the update by returning to Help > About Google Chrome and confirming the version is 109.0.5414.74 or newer
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation0.5 h
- Implementation0.3 h
- Testing0.3 h
- Review / QA0.3 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0140 — 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-2023-0140 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