dbcve.org
ChromeWeb browser · Google

CVE-2023-0139

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-10
Fix available
A fix is available. Upgrade to 109.0.5414.74 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Insufficient validation of untrusted input in Downloads in Google Chrome on Windows prior to 109.0.5414.74 allowed a remote attacker to bypass download 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 confidence

Insufficient validation of untrusted input in Google Chrome's Downloads component on Windows allows a remote attacker to bypass download restrictions through a crafted HTML page. The vulnerability stems from improper handling of untrusted input in the download functionality, enabling attackers to circumvent security controls that normally restrict or warn about certain download types.

MitigationUpdate Google Chrome to version 109.0.5414.74 or later. Organizations should ensure automated browser patching is enabled and verify that download restriction policies remain effective after the update.

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
Affected:< 109.0.5414.74

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Google Chrome installation on Windows
    Check if Chrome is installed by looking in C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe, or query the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome
    Affected if Google Chrome is present on the system
  2. Check installed Chrome version number
    Open Chrome and navigate to chrome://settings/help, or run 'reg query "HKLM\SOFTWARE\Google\Update\Clients" /v pv' in Command Prompt, or examine the chrome.exe file properties
    Affected if The reported version is less than 109.0.5414.74
  3. Verify Windows download restriction policies are active
    Check Group Policy at Computer Configuration > Administrative Templates > Google Chrome > Download restrictions, or inspect the DownloadsPrefetchEnabled and DownloadRestrictions policies in chrome://policy
    Affected if Download restriction policies are configured and Chrome version is below 109.0.5414.74

A Windows user is affected if Google Chrome is installed with a version lower than 109.0.5414.74 and download restriction policies are in place, since the vulnerability allows bypassing those restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 109.0.5414.74 or later
Fixed in 109.0.5414.74
Interim mitigation

Update Google Chrome to version 109.0.5414.74 or later. Organizations should ensure automated browser patching is enabled and verify that download restriction policies remain effective after the update.

Recommended fix High confidence

Chrome 109.0.5414.74 or later

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Chrome will automatically check for and install updates
  3. Ensure the version is 109.0.5414.74 or later
  4. Restart Chrome if an update was installed
  5. Verify the fix by checking chrome://settings/help to confirm the installed version

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
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0139 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-0139 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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