dbcve.org
ChromeWeb browser · Google

CVE-2023-4349

HIGH · 8.8 CVSS v3.1 Published 2023-08-15
Fix available
A fix is available. Upgrade to 116.0.5845.96 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 Device Trust Connectors in Google Chrome prior to 116.0.5845.96 allowed a remote attacker 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

A use-after-free vulnerability exists in Chrome's Device Trust Connectors functionality. A remote attacker can exploit this by tricking a user into visiting a specially crafted HTML page, potentially leading to heap corruption and arbitrary code execution. The vulnerability affects Chrome versions prior to 116.0.5845.96.

MitigationUpdate Google Chrome to version 116.0.5845.96 or later. Organizations should ensure endpoints are running current browser versions through their patch management processes.

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:< 116.0.5845.96
Debian LinuxOperating system
Affected:= 11.0= 12.0
FedoraOperating system
Affected:= 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 if Google Chrome is installed
    On Windows: Look for Chrome in Program Files or check Start Menu. On Linux: Run 'dpkg -l | grep chrome' (Debian) or 'rpm -qa | grep chrome' (Fedora).
    Affected if Chrome browser is present on the system
  2. Determine the installed Chrome version
    On Windows: Right-click chrome.exe and select Properties, or go to chrome://settings/help. On Linux: Run 'google-chrome --version' or 'chromium --version'.
    Affected if A version number is returned showing Chrome is installed
  3. Compare installed version against affected range
    Compare your installed version to 116.0.5845.96. Any version lower than this (e.g., 115.x, 114.x, etc.) is in the affected range.
    Affected if Installed version is less than 116.0.5845.96
  4. Check Linux package version (Debian)
    Run 'apt-cache policy google-chrome-stable' to see the installed and available versions.
    Affected if Installed version shows a number less than 116.0.5845.96
  5. Check Linux package version (Fedora)
    Run 'rpm -qa | grep -i chrome' to list installed Chrome packages, then check version with 'rpm -q --qf '%{VERSION}-%{RELEASE} ' <package-name>'.
    Affected if Installed package version is earlier than 116.0.5845.96

A user is affected if Google Chrome (or Chromium-based browser) version lower than 116.0.5845.96 is installed on the system.

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

Update Google Chrome to version 116.0.5845.96 or later. Organizations should ensure endpoints are running current browser versions through their patch management processes.

Recommended fix High confidence

Chrome 116.0.5845.96 or later (chromium 116.0.5845.96+ on Linux)

  1. Update Google Chrome to version 116.0.5845.96 or later by navigating to Chrome menu > Help > About Google Chrome and clicking 'Update Chrome'
  2. For Linux distributions (Debian 11/12, Fedora 38), run 'sudo apt update && sudo apt upgrade chromium' (Debian) or 'sudo dnf update chromium' (Fedora) to install the patched chromium package
  3. Restart the browser after updating to ensure the fix is applied
  4. Verify the version by navigating to chrome://settings/help - it should show version 116.0.5845.96 or higher

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