dbcve.org
ChromeWeb browser · Google

CVE-2023-2459

MEDIUM · 6.5 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to 113.0.5672.63 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 Prompts in Google Chrome prior to 113.0.5672.63 allowed a remote attacker to bypass permission restrictions 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 · moderate confidence

This is a Chrome browser vulnerability affecting the Prompts implementation. A remote attacker can craft a malicious HTML page that bypasses permission restrictions, potentially allowing unauthorized access to browser features or functions that normally require user confirmation.

MitigationUpdate Google Chrome to version 113.0.5672.63 or later to address the vulnerability. Organizations should ensure browser update deployment across managed endpoints.

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:< 113.0.5672.63
Debian LinuxOperating system
Affected:= 11.0
FedoraOperating system
Affected:= 36= 37= 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 Chrome browser version in the application
    Open Chrome and navigate to chrome://version or click Help > About Google Chrome to view the installed version number
    Affected if The displayed version is earlier than 113.0.5672.63 (for example, 113.0.5672.0 or any 112.x.x.x version)
  2. Check Chrome version via command line
    Open a terminal and run: google-chrome --version or chromium --version
    Affected if The output shows a version number lower than 113.0.5672.63
  3. Check Debian system chromium package version
    On Debian 11 systems, run: dpkg -l | grep chromium or apt list --installed | grep chromium
    Affected if The installed chromium package version is below the fixed version for Debian 11 or the package is present on an unpatched Debian 11 system
  4. Check Fedora system chromium package version
    On Fedora 36, 37, or 38 systems, run: rpm -qa | grep chromium or dnf list installed chromium
    Affected if The installed chromium package version is below the fixed version for the respective Fedora release

A user is affected if their Google Chrome or Chromium browser version is earlier than 113.0.5672.63, particularly on Debian 11, Fedora 36, Fedora 37, or Fedora 38 systems where the browser is installed.

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

Update Google Chrome to version 113.0.5672.63 or later to address the vulnerability. Organizations should ensure browser update deployment across managed endpoints.

Recommended fix High confidence

Chrome 113.0.5672.63 or later (Chrome Stable channel)

  1. Update Google Chrome to version 113.0.5672.63 or later by visiting chrome://settings/help or using your system's package manager
  2. For Fedora systems: Run 'sudo dnf update google-chrome-stable' to install the fixed version
  3. For Debian systems: Run 'sudo apt-get update && sudo apt-get upgrade google-chrome-stable' to install the fixed version
  4. Restart the browser after updating to ensure the fix is applied
  5. Verify the installed version is 113.0.5672.63 or higher by checking chrome://settings/help

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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