dbcve.org
ChromeWeb browser · Google

CVE-2023-4430

HIGH · 8.8 CVSS v3.1 Published 2023-08-23
Fix available
A fix is available. Upgrade to 116.0.5845.110 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 Vulkan in Google Chrome prior to 116.0.5845.110 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 the Vulkan graphics API implementation in Google Chrome versions prior to 116.0.5845.110. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, causing the browser to access freed memory and potentially achieve heap corruption and arbitrary code execution.

MitigationUpdate Google Chrome to version 116.0.5845.110 or later. Enable automatic updates or manually check for updates via chrome://settings/help.

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.110
FedoraOperating system
Affected:= 37= 38= 39
Debian LinuxOperating system
Affected:= 11.0= 12.0

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. Verify Google Chrome installation
    Open chrome://settings/help in the Chrome browser address bar, or run 'google-chrome --version' from command line
    Affected if Chrome is installed and version is displayed
  2. Compare installed version against vulnerable range
    Note the version number shown in chrome://settings_help or from --version command output
    Affected if Version is earlier than 116.0.5845.110 (e.g., 115.x.x.x, 114.x.x.x, etc.)
  3. Check if running a Fedora package
    For Fedora systems, run 'rpm -q google-chrome' to check if the Chrome package from Fedora repositories is installed
    Affected if Package is installed and version check from 'rpm -q --qf "%{VERSION}-%{RELEASE}" google-chrome' shows a version below 116.0.5845.110
  4. Check if running a Debian package
    For Debian systems, run 'dpkg -l | grep google-chrome' to list installed Chrome packages
    Affected if Package is installed and version check from 'dpkg -s google-chrome' shows a version below 116.0.5845.110

You are affected if Google Chrome is installed and the running version is earlier than 116.0.5845.110, regardless of operating 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.110 or later
Fixed in 116.0.5845.110
Interim mitigation

Update Google Chrome to version 116.0.5845.110 or later. Enable automatic updates or manually check for updates via chrome://settings/help.

Recommended fix High confidence

Chrome 116.0.5845.110 or later / Chromium package version 116.0.5845.110 or later

  1. Update Google Chrome to version 116.0.5845.110 or later by navigating to Chrome menu > Help > About Google Chrome and clicking 'Update Google Chrome'
  2. Alternatively, download the latest stable Chrome from the official Google Chrome website (chrome.google.com)
  3. For Linux distributions (Fedora, Debian), run the system package manager update command (e.g., 'sudo dnf update' or 'sudo apt update && sudo apt upgrade') to receive the chromium security patch

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.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-4430 — 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-4430 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