dbcve.org
ChromeWeb browser · Google

CVE-2023-1821

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-04
Fix available
A fix is available. Upgrade to 112.0.5615.49 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 WebShare in Google Chrome prior to 112.0.5615.49 allowed a remote attacker to potentially hide the contents of the Omnibox (URL bar) 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

A flaw in the WebShare API implementation in Google Chrome versions prior to 112.0.5615.49 allowed malicious webpages to obscure or hide the contents of the Omnibox (URL bar), potentially aiding social engineering and phishing attacks by making it difficult for users to verify the legitimate URL they are visiting.

MitigationUpdate Google Chrome to version 112.0.5615.49 or later to patch this 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:< 112.0.5615.49
FedoraOperating system
Affected:= 36= 37
Debian LinuxOperating system
Affected:= 11.0

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
    Open Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help
    Affected if The version displayed is less than 112.0.5615.49
  2. Check Chrome version via command line (Linux)
    Run 'google-chrome --version' or 'chromium --version' in terminal
    Affected if The reported version number is below 112.0.5615.49
  3. Check installed Chrome package on Fedora
    Run 'rpm -qa | grep -i chrome' or 'dnf list installed | grep -i chrome'
    Affected if An installed Chrome package version is shown that is earlier than 112.0.5615.49
  4. Check installed Chrome package on Debian
    Run 'dpkg -l | grep -i chrome' or 'apt list --installed | grep -i chrome'
    Affected if An installed Chrome package version is shown that is earlier than 112.0.5615.49
  5. Verify WebShare API exposure
    Visit any webpage using the WebShare API (navigator.share()) in Chrome and observe whether the Omnibox becomes obscured during the share dialog
    Affected if The URL bar/Omnibox content becomes hidden or obscured while a WebShare dialog is active

You are affected if Google Chrome (or Chromium) version is below 112.0.5615.49 and you use the WebShare API feature in Chrome.

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

Update Google Chrome to version 112.0.5615.49 or later to patch this vulnerability.

Recommended fix High confidence

Chrome 112.0.5615.49 or later (or latest stable channel)

  1. Update Google Chrome to version 112.0.5615.49 or later by navigating to chrome://settings/help and clicking 'Update Google Chrome', or download the latest version from the official Chrome download page
  2. For Fedora systems (36, 37): Run 'dnf update google-chrome-stable' or 'dnf update' to apply system package updates
  3. For Debian Linux 11.0: Run 'apt update && apt upgrade' or 'apt update && apt install google-chrome-stable' to get the patched Chrome package
  4. Restart Chrome after updating to ensure the fix takes effect

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-1821 — 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-1821 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