dbcve.org
ChromeWeb browser · Google

CVE-2023-2135

HIGH · 7.5 CVSS v3.1 Published 2023-04-19
Fix available
A fix is available. Upgrade to 112.0.5615.137 or later.
See remediation →
82/100
Remediation priority · High
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 DevTools in Google Chrome prior to 112.0.5615.137 allowed a remote attacker who convinced a user to enable specific preconditions 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

Use after free vulnerability in Google Chrome's DevTools component allowing a remote attacker to potentially exploit heap corruption via a crafted HTML page. Requires user to enable specific preconditions for exploitation.

MitigationUpdate Google Chrome to version 112.0.5615.137 or later. In enterprise environments, ensure patched browser version is deployed across all 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:< 112.0.5615.137
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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 on Windows, macOS, or Linux
    Open Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' in terminal
    Affected if Version is lower than 112.0.5615.137
  2. Check Chrome package version on Debian 11
    Run 'dpkg -l | grep google-chrome' or 'apt list --installed | grep google-chrome'
    Affected if Package version installed is earlier than 112.0.5615.137-1
  3. Check Chrome package version on Fedora 36-38
    Run 'rpm -qa | grep google-chrome' or 'dnf list installed google-chrome'
    Affected if Package version installed is earlier than 112.0.5615.137-1
  4. Identify if DevTools is accessible or preconditions are enabled
    Since specific preconditions are not publicly detailed, verify if you or your users have enabled remote DevTools debugging, custom DevTools extensions, or non-default DevTools settings
    Affected if Remote DevTools debugging is enabled or non-default DevTools configurations are active

You are affected if Chrome version is below 112.0.5615.137 AND a user has enabled specific DevTools preconditions required for exploitation.

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.137 or later
Fixed in 112.0.5615.137
Interim mitigation

Update Google Chrome to version 112.0.5615.137 or later. In enterprise environments, ensure patched browser version is deployed across all managed endpoints.

Recommended fix High confidence

Chrome 112.0.5615.137 or later (or the latest stable channel release)

  1. Open Google Chrome and navigate to Help > About Google Chrome to check the current version
  2. If the version is below 112.0.5615.137, Chrome will automatically check for and download the update
  3. Click 'Update Google Chrome' if prompted, or wait for the automatic download to complete
  4. Restart Google Chrome to apply the update
  5. For Linux systems (Debian 11.0, Fedora 36/37/38), run the system package manager: 'sudo apt update && sudo apt upgrade' (Debian) or 'sudo dnf update' (Fedora) to update the chrome package
  6. After updating, verify the version by going to chrome://settings/help - it should show 112.0.5615.137 or later

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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