ChromeWeb browser · Google
CVE-2023-6350
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 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 confidenceUse after free vulnerability in libavif library in Google Chrome prior to version 119.0.6045.199 allows a remote attacker to potentially exploit heap corruption via a specially crafted AVIF image file.
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
< 119.0.6045.199
Debian LinuxOperating system
= 11.0= 12.0
FedoraOperating system
= 38= 39CVSS 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.
-
Check Google Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in terminalAffected if Version is earlier than 119.0.6045.199
-
Check libavif library version on DebianRun 'dpkg -l libavif' or 'apt show libavif' in terminalAffected if Package version matches Debian 11.0 or 12.0 and is unpatched
-
Check libavif library version on FedoraRun 'dnf list installed libavif' or 'rpm -qa libavif' in terminalAffected if Package version matches Fedora 38 or 39 and is unpatched
-
Verify Chrome's AVIF image handling capabilityOpen any AVIF image file in Chrome or inspect if the Chrome build includes libavif support (check chrome://components)Affected if Chrome can render AVIF images and version is before 119.0.6045.199
You are affected if you run Google Chrome before version 119.0.6045.199 or have an unpatched libavif library on Debian 11/12 or Fedora 38/39 that can process AVIF images.
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 · scoped119.0.6045.199
Update Google Chrome to version 119.0.6045.199 or later to remediate the vulnerability.
Chrome/Chromium 119.0.6045.199 or later
- For Chrome users: Open Chrome, go to Settings > About Chrome, and verify version is 119.0.6045.199 or later; if not, click 'Update Google Chrome'
- For Chromium on Debian 11/12: Run 'sudo apt update && sudo apt upgrade' or 'sudo apt install chromium' to get the latest version
- For Chromium on Fedora 38/39: Run 'sudo dnf update' to apply security updates to the chromium package
- Alternatively, manually download Chrome 119.0.6045.199 or later from official Google channels
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
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 locallyCheck whether your project pulls in CVE-2023-6350 — 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-6350 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