ChromeWeb browser · Google
CVE-2023-0928
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 SwiftShader in Google Chrome prior to 110.0.5481.177 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 SwiftShader (Google's software graphics rasterizer) in Google Chrome allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. The vulnerability occurs when memory is accessed after being freed, leading to unpredictable behavior and potential code execution.
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
< 110.0.5481.177CVSS 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.
-
Verify Google Chrome is installedCheck for Chrome installation: on Windows look in Program Files/Google/Chrome/Application/chrome.exe, on macOS check /Applications/Google Chrome.app, on Linux check /usr/bin/google-chrome or /opt/google/chrome/google-chromeAffected if Chrome is not installed - the CVE does not apply
-
Determine installed Chrome versionOpen chrome://version in the Chrome address bar or run 'google-chrome --version' from command line. Record the version number shown (e.g., 110.0.5481.100)Affected if The installed version is less than 110.0.5481.177 (for example, 109.x.x.x or 110.0.5481.100)
-
Check if SwiftShader is actively usedNavigate to chrome://gpu in Chrome and look for 'SwiftShader' listed under the 'Graphics' or 'Driver' information section. Also check chrome://flags for any enabled flags that force software rendering like 'Override software rendering' or check command line for --disable-gpu or --use-gl=swiftshader flagsAffected if SwiftShader is listed as active or being used for rendering (this confirms the vulnerable component is in use)
You are affected if Chrome is installed with a version below 110.0.5481.177 AND SwiftShader is being used for graphics rendering on your system
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 · scoped110.0.5481.177
Update Google Chrome to version 110.0.5481.177 or later to patch the SwiftShader vulnerability.
Chrome 110.0.5481.177 or later
- Open Chrome and navigate to Settings > Help > About Google Chrome to check the current version
- If the version is below 110.0.5481.177, Chrome will automatically check for and apply updates
- Restart Chrome after the update completes to ensure the fix is applied
- Alternatively, download the latest Chrome version from the official Google Chrome website (chrome.com) to ensure you have version 110.0.5481.177 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
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0928 — 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-0928 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