ChromeWeb browser · Google
CVE-2023-2929
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 · uneditedOut of bounds write in Swiftshader in Google Chrome prior to 114.0.5735.90 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 confidenceOut-of-bounds write vulnerability in Swiftshader (Google's software WebGL renderer) in Google Chrome versions prior to 114.0.5735.90. A remote attacker can exploit this by enticing users to visit a crafted HTML page, potentially leading to heap corruption and possible 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
< 114.0.5735.90CVSS 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.
-
Check installed Google Chrome versionNavigate to chrome://settings/help or use 'Help > About Google Chrome' to view the version number. On Windows, you can also right-click the Chrome shortcut and select Properties > Details. On Linux, run 'google-chrome --version' or 'google-chrome-stable --version' in terminal.Affected if The displayed version is less than 114.0.5735.90 (e.g., 113.x.x.x or earlier)
-
Verify WebGL is accessibleOpen chrome://gpu/ and look for 'WebGL' in the 'Graphics Feature Status' section. WebGL may be enabled by default; confirm it shows as 'Hardware accelerated' or 'Software only' (the latter indicates Swiftshader is in use).Affected if WebGL is listed as available or enabled (Swiftshader is used when hardware acceleration is unavailable or as a fallback)
-
Confirm Swiftshader is in useVisit a WebGL-enabled website or open chrome://gpu/ and check if the 'SwiftShader' driver is listed under Graphics Feature Status or in the 'Driver Information' section.Affected if Swiftshader is actively being used as the WebGL renderer (particularly in software rendering mode)
You are affected if you are running Google Chrome version 114.0.5735.90 or lower AND WebGL/Swiftshader is enabled 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 · scoped114.0.5735.90
Update Google Chrome to version 114.0.5735.90 or later. Apply organizational patch management processes to ensure all Chrome installations are updated.
Chrome 114.0.5735.90 or later (stable channel)
- 1. Open Google Chrome on your system
- 2. Navigate to Chrome menu > Help > About Google Chrome
- 3. The About Chrome page will automatically check for updates
- 4. If an update is available, click 'Update Google Chrome'
- 5. Restart the browser to apply the update
- 6. Verify the version by returning to Help > About Google Chrome and confirm it shows version 114.0.5735.90 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-2929 — 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-2929 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