ChromeWeb browser · Google
CVE-2019-5771
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 · uneditedAn incorrect JIT of GLSL shaders in SwiftShader in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to execute arbitrary code 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 · high confidenceA JIT (Just-In-Time) compilation flaw in SwiftShader's GLSL (OpenGL Shading Language) shader compiler in Google Chrome allows a remote attacker to achieve arbitrary code execution through a specially crafted HTML page containing malicious shader code.
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
< 72.0.3626.81
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0
FedoraOperating system
= 29= 30CVSS 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.0/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 if Google Chrome is installedCheck for Chrome binary location: Windows - C:\Program Files\Google\Chrome\Application\chrome.exe, macOS - /Applications/Google Chrome.app/Contents/MacOS/Google Chrome, Linux - /usr/bin/google-chrome or /opt/google/chrome/google-chromeAffected if Google Chrome browser is present on the system
-
Identify installed Chrome versionRun 'google-chrome --version' on Linux/Mac, or check Chrome's 'About Google Chrome' dialog on Windows. The version number will be displayed (for example, 72.0.3626.81 or earlier)Affected if The installed version is lower than 72.0.3626.81 (for example, 71.x.x.x or earlier)
-
Verify if SwiftShader software renderer is in useNavigate to chrome://gpu in Chrome browser and look for 'SwiftShader' under Graphics Feature Status, or check if the system is using software rendering (GPU hardware acceleration disabled)Affected if SwiftShader is listed as active for GL or software rendering is enabled; however, the JIT flaw exists in the SwiftShader component regardless of active use when the affected Chrome version is present
A system is affected if Google Chrome version is lower than 72.0.3626.81 and the SwiftShader component (software renderer) is present in the Chrome installation, as the vulnerable GLSL shader compiler code exists regardless of whether it is actively invoked.
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 data72.0.3626.81
Update Google Chrome to version 72.0.3626.81 or later, which contains the patched SwiftShader component; enterprise deployments should verify complete coverage across all clients using the software renderer.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5771 — 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-5771 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