dbcve.org
ChromeWeb browser · Google

CVE-2023-4350

MEDIUM · 6.5 CVSS v3.1 Published 2023-08-15
Fix available
A fix is available. Upgrade to 116.0.5845.96 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 Fullscreen in Google Chrome on Android prior to 116.0.5845.96 allowed a remote attacker to potentially spoof the contents of the Omnibox (URL bar) via a crafted HTML page. (Chromium security severity: High)

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

Inappropriate implementation in Chrome's Fullscreen mode on Android allows a remote attacker to spoof the Omnibox (URL bar) contents via a crafted HTML page. The vulnerability stems from how fullscreen mode handles the display of the URL bar, potentially tricking users into believing they're on a legitimate site when the actual URL is different.

MitigationUpdate Google Chrome for Android to version 116.0.5845.96 or later to address the fullscreen mode implementation flaw that enables URL bar spoofing.

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:< 116.0.5845.96
Debian LinuxOperating system
Affected:= 11.0= 12.0
FedoraOperating system
Affected:= 38

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 Google Chrome version on Android
    Navigate to Settings > Help > About Chrome on the Android device to view the installed version number
    Affected if The installed version is lower than 116.0.5845.96 and the browser is Chrome on Android with fullscreen mode available
  2. Identify if Chromium-based browser is in use on Linux
    Run 'chromium --version' or 'chromium-browser --version' in the terminal to check the installed Chromium version
    Affected if The installed version is lower than 116.0.5845.96 and the browser supports fullscreen mode features
  3. Check for fullscreen API usage
    Inspect any web content that requests fullscreen mode via the Fullscreen API, particularly on Android browsers
    Affected if Fullscreen mode is enabled and the browser version is below 116.0.5845.96, allowing potential URL bar spoofing
  4. Verify Chrome distribution source
    On Android, check if the browser is Google Chrome (not a third-party Chromium-based browser) by examining the app package name in Settings > Apps
    Affected if The affected browser is Google Chrome for Android versions below 116.0.5845.96

You are affected if you are running Google Chrome on Android with a version lower than 116.0.5845.96, or a Chromium browser on Linux with a version lower than 116.0.5845.96 that utilizes fullscreen mode features.

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 116.0.5845.96 or later
Fixed in 116.0.5845.96
Interim mitigation

Update Google Chrome for Android to version 116.0.5845.96 or later to address the fullscreen mode implementation flaw that enables URL bar spoofing.

Recommended fix High confidence

Chrome 116.0.5845.96 or later (stable release)

  1. Check current Chrome version by navigating to chrome://settings/help
  2. Update Chrome through the browser's built-in update mechanism (Menu > Help > About Google Chrome)
  3. Alternatively, update via system package manager: For Debian/Ubuntu run 'sudo apt update && sudo apt upgrade chrome', For Fedora run 'sudo dnf update google-chrome-stable'
  4. Restart Chrome after update completes
  5. Verify the installed version is 116.0.5845.96 or later by visiting chrome://settings/help

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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