dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 21 Dec 2023.
ChromeWeb browser · Google

CVE-2023-6345

CRITICAL · 9.6 CVSS v3.1 Published 2023-11-29
Fix available
A fix is available. Upgrade to 119.0.2151.97 / 119.0.6045.199 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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
Integer overflow in Skia in Google Chrome prior to 119.0.6045.199 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a malicious file. (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

Integer overflow vulnerability in Skia (Google's 2D graphics library) in Chrome prior to version 119.0.6045.199. An attacker who has already compromised the renderer process can trigger the overflow via a malicious file, potentially escaping Chrome's sandbox security boundary.

MitigationUpdate Google Chrome to version 119.0.6045.199 or later. In enterprise environments, deploy the update through patch management systems and verify completion across all 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:< 119.0.6045.199
Debian LinuxOperating system
Affected:= 11.0= 12.0
FedoraOperating system
Affected:= 37= 38= 39
Edge ChromiumWeb browser
Affected:< 119.0.2151.97

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Google Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome. Alternatively, navigate to chrome://version in the address bar.
    Affected if The version displayed is earlier than 119.0.6045.199
  2. Check Microsoft Edge version
    Open Edge, click the three-dot menu > Help and feedback > About Microsoft Edge. Alternatively, navigate to edge://version in the address bar.
    Affected if The version displayed is earlier than 119.0.2151.97
  3. Check installed Chrome package on Linux (Debian)
    Run `dpkg -l | grep google-chrome` or check /opt/google/chrome/ directory for the version file.
    Affected if The installed version is earlier than 119.0.6045.199 or the package is not found (meaning Chrome may not be installed)
  4. Check installed Chrome package on Linux (Fedora)
    Run `rpm -q google-chrome` or check the installed package version.
    Affected if The installed version is earlier than 119.0.6045.199 or the package is not found

You are affected if you run Google Chrome before 119.0.6045.199 or Microsoft Edge before 119.0.2151.97, or if you have Chrome installed on Debian 11/12 or Fedora 37/38/39 without an update.

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 119.0.2151.97 / 119.0.6045.199 or later
Fixed in 119.0.2151.97119.0.6045.199
Interim mitigation

Update Google Chrome to version 119.0.6045.199 or later. In enterprise environments, deploy the update through patch management systems and verify completion across all endpoints.

Recommended fix High confidence

Chrome 119.0.6045.199 or later; Edge Chromium 119.0.2151.97 or later; patched Skia packages via Linux distribution package managers

  1. Update Google Chrome to version 119.0.6045.199 or later by navigating to chrome://settings/help and clicking 'Update Chrome', or download from official Chrome release channels
  2. Update Microsoft Edge to version 119.0.2151.97 or later via Edge settings or download from official Microsoft Edge channels
  3. For Linux systems: Run 'sudo apt update && sudo apt upgrade' on Debian-based systems (Debian 11, 12) to install patched Skia package
  4. For Linux systems: Run 'sudo dnf update' on Fedora systems (Fedora 37, 38, 39) to install patched Skia package
  5. Restart all browser instances after updating to ensure the patched version is loaded
Caveat Minimal risk - browser and Skia library updates typically have no breaking changes for end users; Linux package updates may include other security patches

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get it fixed fast

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