ChromeWeb browser · Google
CVE-2023-6346
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 WebAudio in Google Chrome prior to 119.0.6045.199 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 confidenceUse-after-free vulnerability in Google Chrome's WebAudio component allowing a remote attacker to exploit heap corruption via a crafted HTML page. The flaw exists in all versions prior to 119.0.6045.199.
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 installed Google Chrome version on Windows or macOSOpen Chrome, click the three-dot menu (top right), select 'Help', then 'About Google Chrome'. The version number is displayed on the page that opens.Affected if The displayed version is lower than 119.0.6045.199
-
Check installed Chrome version on Linux via command lineRun 'google-chrome --version' or 'chromium --version' in a terminal to retrieve the installed version number.Affected if The returned version is lower than 119.0.6045.199
-
Check Debian package versionRun 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable' to see the installed package version.Affected if The installed version number is less than 119.0.6045.199
-
Check Fedora/RHEL package versionRun 'rpm -qa | grep chrome' or 'dnf list installed | grep chrome' to see the installed Chrome package version.Affected if The installed version number is less than 119.0.6045.199
You are affected if the installed Google Chrome version is lower than 119.0.6045.199, as the use-after-free vulnerability in WebAudio exists in all prior versions.
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 119.0.6045.199 (or later stable release)
- For Chrome Desktop users: Navigate to Chrome menu > Help > About Google Chrome and update to version 119.0.6045.199 or later
- For Debian Linux (11, 12): Run 'sudo apt update && sudo apt upgrade' to install the patched chromium package version 119.0.6045.199-1 or later
- For Fedora (38, 39): Run 'sudo dnf update chromium' to install the patched chromium package version 119.0.6045.199-1 or later
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
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-6346 — 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-6346 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