dbcve.org
ChromeWeb browser · Google

CVE-2023-6351

HIGH · 8.8 CVSS v3.1 Published 2023-11-29
Fix available
A fix is available. Upgrade to 119.0.6045.199 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 libavif in Google Chrome prior to 119.0.6045.199 allowed a remote attacker to potentially exploit heap corruption via a crafted avif 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

A use-after-free vulnerability exists in libavif (an AVIF image decoding library) bundled with Google Chrome versions prior to 119.0.6045.199. A remote attacker can exploit this by tricking a user into opening a specially crafted malicious AVIF image file, potentially leading to heap corruption and arbitrary code execution.

MitigationUpdate Google Chrome to version 119.0.6045.199 or later, or ensure automatic updates are enabled and applied. Alternatively, disable AVIF image rendering in Chrome if immediate updating is not feasible.

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:= 38= 39

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 Google Chrome version
    Navigate to chrome://settings/help or look at 'About Google Chrome' in the Chrome menu to see the installed version number
    Affected if Version is lower than 119.0.6045.199 (e.g., 119.0.6045.105, 118.x, etc.)
  2. Check if AVIF image rendering is enabled in Chrome
    Navigate to chrome://flags/#enable-avif and observe the flag status; alternatively check if Chrome has automatically enabled AVIF decoding
    Affected if AVIF decoding is enabled and the Chrome version is vulnerable (below 119.0.6045.199)
  3. Check installed libavif library version on Debian
    Run 'dpkg -l libavif*' or 'apt show libavif' in terminal to list the installed libavif package version
    Affected if libavif version is present and corresponds to the bundled version in a vulnerable Chrome (Debian 11.0 or 12.0 shipped with vulnerable libavif)
  4. Check installed libavif library version on Fedora
    Run 'rpm -qa | grep libavif' or 'dnf info libavif' in terminal to list the installed libavif package version
    Affected if libavif version corresponds to Fedora 38 or 39 packages which are affected

User is affected if running Chrome version below 119.0.6045.199 with AVIF rendering enabled, or running Debian 11/12 or Fedora 38/39 with the vulnerable libavif library version present.

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.6045.199 or later
Fixed in 119.0.6045.199
Interim mitigation

Update Google Chrome to version 119.0.6045.199 or later, or ensure automatic updates are enabled and applied. Alternatively, disable AVIF image rendering in Chrome if immediate updating is not feasible.

Recommended fix High confidence

Chrome 119.0.6045.199 or later (stable channel)

  1. Update Google Chrome to version 119.0.6045.199 or later
  2. On Linux systems, run system package manager update: 'apt-get update && apt-get upgrade' for Debian-based systems, or 'dnf update' for Fedora-based systems
  3. Verify the Chrome version by navigating to chrome://settings/help to confirm the update was applied
  4. Restart the browser to ensure the fix is fully applied

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