dbcve.org
ChromeWeb browser · Google

CVE-2023-0932

HIGH · 8.8 CVSS v3.1 Published 2023-02-22
Fix available
A fix is available. Upgrade to 110.0.5481.177 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Use after free in WebRTC in Google Chrome on Windows prior to 110.0.5481.177 allowed a remote attacker who convinced the user to engage in specific UI interactions 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 confidence

Use-after-free vulnerability in WebRTC component of Google Chrome on Windows before version 110.0.5481.177. Remote attacker can craft a malicious HTML page that, when the user performs specific UI interactions, triggers a use-after-free condition leading to potential heap corruption.

MitigationUpgrade Google Chrome to version 110.0.5481.177 or later on all Windows systems. This is a client-side browser vulnerability that requires no code changes—only updating the browser.

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
Affected:< 110.0.5481.177

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Google Chrome is installed on Windows
    Open Windows Settings > Apps > Apps & features, or run 'Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome"' in PowerShell to check for Chrome installation.
    Affected if Google Chrome is not found on the system, the vulnerability does not apply.
  2. Determine installed Google Chrome version
    Open Chrome, navigate to chrome://settings/help, or run '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' in Command Prompt/PowerShell to retrieve the version number.
    Affected if The version number is displayed and can be compared to the affected range.
  3. Compare version against affected range
    Compare the installed version number to 110.0.5481.177. Versions below 110.0.5481.177 are affected; version 110.0.5481.177 and later are not affected.
    Affected if Installed version is less than 110.0.5481.177, indicating the system is vulnerable.
  4. Confirm Windows platform
    This vulnerability specifically affects Google Chrome on Windows. Verify the operating system by running 'winver' or checking System Properties.
    Affected if The vulnerability only applies to Chrome on Windows; other operating systems are not affected by this specific CVE.

A user is affected if Google Chrome is installed on Windows and the installed version is below 110.0.5481.177.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 110.0.5481.177 or later
Fixed in 110.0.5481.177
Interim mitigation

Upgrade Google Chrome to version 110.0.5481.177 or later on all Windows systems. This is a client-side browser vulnerability that requires no code changes—only updating the browser.

Recommended fix High confidence

Chrome 110.0.5481.177 or later

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. Chrome will automatically check for updates and download version 110.0.5481.177 or later
  6. Click 'Relaunch' or restart the browser manually to apply the update
  7. Verify the update was successful by returning to About Google Chrome and confirming the version is 110.0.5481.177 or higher
Caveat Chrome updates typically have minimal breaking changes; however, some legacy extensions or older system configurations may experience temporary compatibility issues

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
  • Testing0.5 h
  • Review / QA0.5 h
3.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0932 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-0932 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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