dbcve.org
ChromeWeb browser · Google

CVE-2023-0132

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
Inappropriate implementation in in Permission prompts in Google Chrome on Windows prior to 109.0.5414.74 allowed a remote attacker to force acceptance of a permission prompt 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 confidence

This vulnerability in Google Chrome on Windows versions prior to 109.0.5414.74 allows a remote attacker to force acceptance of permission prompts (such as camera, microphone, or location access) via a crafted HTML page. The issue stems from an inappropriate implementation in the permission prompt handling logic, enabling an attacker to bypass user consent mechanisms and automatically grant permissions without genuine user authorization.

MitigationUpdate Google Chrome to version 109.0.5414.74 or later on all Windows systems. Organizations should ensure patch management processes include browser updates and may want to review granted site permissions in Chrome settings.

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. Verify Google Chrome is installed on the Windows system
    Open Control Panel > Programs and Features, or open Settings > Apps > Apps & features, and look for Google Chrome in the installed programs list
    Affected if Google Chrome is present on the Windows system
  2. Determine the installed Google Chrome version
    Open Google Chrome, click the three-dot menu in the top-right corner, go to Help > About Google Chrome. The version number is displayed on this page
    Affected if The displayed version is less than 109.0.5414.74
  3. Confirm the Chrome channel type
    In the About Google Chrome page, note whether the version shown is Stable, Beta, Dev, or Canary. Stable versions follow the format mentioned in the advisory
    Affected if The installed version is a Stable channel release prior to 109.0.5414.74
  4. Verify the Windows platform
    This vulnerability specifically affects Google Chrome on Windows. Confirm the operating system is Windows by checking System Properties or Settings > System > About
    Affected if The system is running Windows and Chrome version is below 109.0.5414.74

If Google Chrome is installed on a Windows system and the version is earlier than 109.0.5414.74, the environment is affected by this permission prompt bypass vulnerability.

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 on all Windows systems. Organizations should ensure patch management processes include browser updates and may want to review granted site permissions in Chrome settings.

Recommended fix High confidence

Chrome 109.0.5414.74 or later

  1. Open Google Chrome on Windows
  2. Navigate to Settings > Help > About Google Chrome (or enter chrome://settings/help in the address bar)
  3. Chrome will automatically check for updates
  4. If version 109.0.5414.74 or later is available, click 'Update Google Chrome'
  5. Restart the browser to apply the update
  6. Verify the update by returning to About Google Chrome and confirming the version is 109.0.5414.74 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Review / QA1.0 h
2.0 hours of engineering $750
Get the upgrade done

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

Check whether your project pulls in CVE-2023-0132 — 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-0132 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