ChromeWeb browser · Google
CVE-2023-2723
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 · uneditedUse after free in DevTools in Google Chrome prior to 113.0.5672.126 allowed a remote attacker who had compromised the renderer process 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 confidenceUse-after-free vulnerability in Chrome DevTools that allows a remote attacker with compromised renderer process to potentially exploit heap corruption via malicious HTML page.
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
< 113.0.5672.126
Debian LinuxOperating system
= 11.0
FedoraOperating system
= 37= 38CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome is installedCheck for Chrome executable: On Windows, look in Program Files/Google/Chrome/Application/ or check via registry. On macOS, check /Applications/Google Chrome.app. On Linux, run which google-chrome or check /usr/bin/google-chromeAffected if Chrome browser is present on the system
-
Determine installed Chrome versionOpen Chrome, go to Settings > About Chrome, or navigate to chrome://settings/help. Alternatively, run 'google-chrome --version' from command line on Linux/macOS, or check the executable properties on WindowsAffected if Version displayed is below 113.0.5672.126
-
Confirm browser is actively usedThis vulnerability is triggered when a user visits a malicious HTML page while Chrome is running with DevTools open or previously openedAffected if Users run Chrome to browse web pages and the version is in the affected range
You are affected if Google Chrome with a version lower than 113.0.5672.126 is installed and used to browse web pages, as the vulnerability can be triggered via compromised renderer processes from malicious web content.
Generated from the published advisory. Verify against your own configuration.
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 · scoped113.0.5672.126
Update Google Chrome to version 113.0.5672.126 or later to patch the vulnerability.
Chrome 113.0.5672.126 (or later stable release)
- Check current Chrome version by navigating to chrome://settings/help or chrome://about
- If version is less than 113.0.5672.126, update Chrome to the latest version using the browser's built-in update mechanism
- For Debian Linux 11.0: Run 'sudo apt-get update && sudo apt-get upgrade' to install the updated chromium package
- For Fedora 37/38: Run 'sudo dnf update' to install the updated chromium package
- Restart Chrome after updating to ensure the fix is applied
- Verify the version is now 113.0.5672.126 or later 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
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-2723 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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