dbcve.org
ChromeWeb browser · Google

CVE-2023-0133

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 Android prior to 109.0.5414.74 allowed a remote attacker to bypass main origin permission delegation 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 for Android allows a remote attacker to bypass main origin permission delegation through crafted HTML pages, potentially enabling unauthorized access to sensitive device permissions.

MitigationUpdate Google Chrome for Android to version 109.0.5414.74 or later to patch the permission prompt bypass vulnerability.

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. Check if Google Chrome for Android is installed
    Open the device Settings, go to Apps, and look for Chrome in the app list, or check the Chrome app icon on the home screen
    Affected if Google Chrome for Android is present on the device
  2. Determine the installed Chrome version
    Open Chrome, tap the three-dot menu, go to Settings, then About Chrome. The version number is displayed at the top of the screen
    Affected if The displayed version number is lower than 109.0.5414.74
  3. Confirm the vulnerability scope
    Verify that the Chrome version shown is a stable release and not a beta, dev, or canary build
    Affected if The installed version is a stable release below 109.0.5414.74

A user is affected if Google Chrome for Android is installed with a stable version lower than 109.0.5414.74

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 for Android to version 109.0.5414.74 or later to patch the permission prompt bypass vulnerability.

Recommended fix High confidence

109.0.5414.74

  1. Open Google Play Store on the Android device
  2. Search for "Google Chrome"
  3. Tap the "Update" button to install version 109.0.5414.74 or later
  4. Alternatively, open Chrome > tap the three dots menu > tap "Settings" > tap "About Chrome" to trigger automatic update check

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.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-0133 — 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-0133 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