ChromeWeb browser · Google
CVE-2023-5473
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 Cast in Google Chrome prior to 118.0.5993.70 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Low)
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 · moderate confidenceUse-after-free vulnerability in Google Chrome's Cast functionality prior to version 118.0.5993.70. A remote attacker who has already compromised the renderer process can exploit this vulnerability via a crafted HTML page to potentially exploit heap corruption.
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
< 118.0.5993.70
Debian LinuxOperating system
= 11.0= 12.0CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
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 Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in terminal to see the exact version numberAffected if Version is below 118.0.5993.70
-
Verify Cast extension or plugin is presentNavigate to chrome://extensions or chrome://components and look for 'Cast' or 'Chrome Cast' entryAffected if Cast extension or component is installed and enabled
-
Confirm Cast feature is enabledLook for the Cast icon in the Chrome toolbar, or check chrome://settings/handlers for Cast-related settingsAffected if Cast feature is actively enabled in the browser settings
-
Identify if browser handles untrusted web contentReview whether Chrome is used for general web browsing, especially visiting untrusted websites, or if it is restricted to trusted internal resources onlyAffected if Browser regularly accesses untrusted or external web content where a compromised renderer could be introduced
You are affected if your Chrome version is below 118.0.5993.70 AND the Cast feature is enabled AND your browser processes untrusted web content that could introduce a compromised renderer process.
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 · scoped118.0.5993.70
Update Google Chrome to version 118.0.5993.70 or later. Since exploitation requires a compromised renderer process, ensure browsers are kept updated and consider restricting access to untrusted content.
Chrome 118.0.5993.70
- Check current Chrome version by navigating to chrome://settings/help
- Download and install Chrome version 118.0.5993.70 or later from the official Chrome release channel (https://www.google.com/chrome/)
- Restart Chrome after the update to complete the installation
- Verify the update was successful by checking chrome://settings/help again
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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-5473 — 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-5473 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