ChromeWeb browser · Google
CVE-2023-6347
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 Mojo 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 the Mojo IPC (Inter-Process Communication) framework in Google Chrome allows a remote attacker to access freed memory, potentially leading to heap corruption and arbitrary code execution, delivered via a malicious crafted HTML page.
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.
-
Identify installed Chrome browserOpen Chrome, click the three-dot menu, select 'Help', then 'About Google Chrome'. The version number will be displayed on that page.Affected if Google Chrome is installed and the version shown is less than 119.0.6045.199
-
Check Chrome version via command line (Linux)Run 'google-chrome --version' or 'chromium --version' in a terminal to get the exact version number.Affected if The command returns a version lower than 119.0.6045.199
-
Check package manager version (Debian)Run 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable' to see the installed Chrome package version.Affected if The installed version is below 119.0.6045.199
-
Check package manager version (Fedora)Run 'dnf list installed google-chrome-stable' or 'rpm -qa | grep chrome' to see the installed Chrome package version.Affected if The installed version is below 119.0.6045.199
You are affected if Google Chrome (any installed variant) is present with a version number below 119.0.6045.199.
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 patch the vulnerability. Organizations should deploy browser updates through their patch management infrastructure.
119.0.6045.199
- Update Google Chrome to version 119.0.6045.199 or later by visiting chrome://settings/help and clicking 'Update Google Chrome', or download the latest version from the official Google Chrome website
- For Debian-based Linux distributions (Debian 11/12): Run 'sudo apt update && sudo apt upgrade' to install the updated chromium package containing the security fix
- For Fedora Linux (38/39): Run 'sudo dnf update' to install the updated chromium package containing the security fix
- Restart the browser after updating to apply the fix
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6347 — 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-6347 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