dbcve.org
ChromeWeb browser · Google

CVE-2023-2725

HIGH · 8.8 CVSS v3.1 Published 2023-05-16
Fix available
A fix is available. Upgrade to 113.0.5672.126 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Use after free in Guest View in Google Chrome prior to 113.0.5672.126 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption 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

This is a use-after-free vulnerability in Google Chrome's Guest View feature (used for running web apps in isolated contexts) that exists prior to version 113.0.5672.126. An attacker must first convince a user to install a malicious extension, which can then trigger the vulnerability when the user visits a crafted HTML page, potentially leading to heap corruption and arbitrary code execution.

MitigationUpdate Google Chrome to version 113.0.5672.126 or later. Additionally, enforce policies restricting extension installation to trusted sources only and educate users about the risks of installing extensions from untrusted origins.

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.126
Debian LinuxOperating system
Affected:= 11.0
FedoraOperating system
Affected:= 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 installed Chrome version
    Navigate to chrome://settings/help or click Help > About Google Chrome to view the current version number
    Affected if The displayed version is less than 113.0.5672.126
  2. Review installed extensions
    Navigate to chrome://extensions/ and examine all installed extensions. Look for any unfamiliar, unsigned, or recently added extensions from untrusted sources
    Affected if Any extension is present that was installed from outside the Chrome Web Store or from an unknown/untrusted developer
  3. Verify extension installation policy
    Check if your organization or browser has policies restricting extension installation. On Chrome, navigate to chrome://policy/ and look for ExtensionInstallForcelist, ExtensionInstallSources, or similar extension control policies
    Affected if No restrictive extension policies are configured and users can install arbitrary extensions
  4. Check for Guest View usage
    Guest View in Chrome is typically used by enterprise apps or specific web applications. Review any installed PWAs or enterprise applications that may utilize the Guest View feature
    Affected if Applications utilizing Guest View are in use and the Chrome version is vulnerable
  5. Identify Linux distribution version (if applicable)
    For Debian 11 or Fedora 37/38 users, run 'cat /etc/os-release' or 'hostnamectl' to confirm the exact distribution version
    Affected if Running Debian 11, Fedora 37, or Fedora 38 with a vulnerable Chrome/Chromium version installed

You are affected if Chrome version is below 113.0.5672.126 AND a malicious or untrusted extension has been installed that could trigger the Guest View use-after-free.

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.126 or later
Fixed in 113.0.5672.126
Interim mitigation

Update Google Chrome to version 113.0.5672.126 or later. Additionally, enforce policies restricting extension installation to trusted sources only and educate users about the risks of installing extensions from untrusted origins.

Recommended fix High confidence

Chrome 113.0.5672.126 or later (or distribution-specific chromium package updates that include the security fix)

  1. Update Google Chrome to version 113.0.5672.126 or later. Open Chrome, go to Help > About Google Chrome to check for updates and install any available updates.
  2. For Debian 11.0 systems: Run 'sudo apt-get update && sudo apt-get upgrade' to update the chromium package
  3. For Fedora 37/38 systems: Run 'sudo dnf update' to update the chromium package
  4. Restart Chrome or the browser after updating to ensure the fix is applied

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