ChromeWeb browser · Google
CVE-2023-0472
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 WebRTC in Google Chrome prior to 109.0.5414.119 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 WebRTC (Web Real-Time Communication) component of Google Chrome allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. The vulnerability exists prior to version 109.0.5414.119.
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
< 109.0.5414.119CVSS 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.
-
Determine installed Chrome versionOpen Chrome and navigate to chrome://version, or click Help > About Google Chrome. Note the version number displayed.Affected if The installed version is lower than 109.0.5414.119 (e.g., 109.0.5414.74, 108.x.x.x, etc.)
-
Confirm WebRTC component presenceWebRTC is built into Chrome and enabled by default. To verify it is active, open chrome://webrtc-internals and check if the page loads without errors, indicating WebRTC internals are accessible.Affected if WebRTC is accessible and the Chrome version is below 109.0.5414.119
-
Compare version against CVE thresholdCompare the full version string from step 1 against 109.0.5414.119. The format is MAJOR.MINOR.BUILD.PATCH (e.g., 109.0.5414.74 < 109.0.5414.119).Affected if The patch version (fourth number) is less than 119 while the major version is 109, or the major version is below 109
A user is affected if Google Chrome version is below 109.0.5414.119 and WebRTC is enabled (default state), allowing a remote attacker to trigger the use-after-free via a crafted HTML page.
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 · scoped109.0.5414.119
Update Google Chrome to version 109.0.5414.119 or later to patch the use-after-free vulnerability in WebRTC.
109.0.5414.119 or later
- Open Google Chrome
- Click the menu icon (three dots) in the top-right corner
- Select 'Help' then 'About Google Chrome'
- Chrome will check for updates and automatically download version 109.0.5414.119 or later
- Click 'Relaunch' to restart Chrome and apply the update
- Verify the update by returning to About Google Chrome and confirming the version is 109.0.5414.119 or higher
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-0472 — 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-0472 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