ChromeWeb browser · Google
CVE-2019-5835
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 · uneditedObject lifecycle issue in SwiftShader in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.
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 confidenceObject lifecycle vulnerability in SwiftShader (Google's software WebGL renderer) allows a remote attacker to achieve out-of-bounds memory access via a malicious HTML page. The issue stems from improper handling of object lifetimes in the graphics rendering component, enabling memory 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
< 75.0.3770.80
FedoraOperating system
= 29= 30= sle-15= 15.0= 15.1= 42.3CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 Google Chrome versionNavigate to chrome://version in the browser address bar, or run `google-chrome --version` (or `chromium --version`) in a terminalAffected if version is below 75.0.3770.80 (for example, 74.x.x)
-
Verify WebGL is enabledNavigate to chrome://flags in the browser and search for 'WebGL' or visit a WebGL test page (such as webgl.org)Affected if WebGL is enabled and actively used in the browser
-
Confirm SwiftShader is in useNavigate to chrome://gpu and look under 'Graphics' or 'WebGL' for 'SwiftShader' as the renderer or driverAffected if SwiftShader is listed as the active WebGL software renderer
-
Check operating system version (if on Linux)Run `cat /etc/os-release` or `uname -r` to identify the Linux distribution and versionAffected if Running Fedora 29 or 30, openSUSE Leap 15.0/15.1/42.3, or openSUSE Backports SLE-15 with an affected Chrome version
A user is affected if running Google Chrome version below 75.0.3770.80 with WebGL enabled and SwiftShader active as the software WebGL renderer.
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.
From vendor data75.0.3770.80
Update Google Chrome to version 75.0.3770.80 or later to incorporate the patched SwiftShader component. Users should also ensure SwiftShader updates are applied through Chrome's internal update mechanism.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5835 — 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-2019-5835 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