ChromeWeb browser · Google
CVE-2019-5836
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 · uneditedHeap buffer overflow in ANGLE in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potentially exploit heap corruption 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 confidenceHeap buffer overflow vulnerability in the ANGLE graphics library in Google Chrome versions prior to 75.0.3770.80 allows remote attackers to exploit heap corruption via a crafted HTML page.
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
Debian LinuxOperating system
= 10.0
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
- 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 versionOpen chrome://version in the browser address bar, or run 'google-chrome --version' or 'chromium --version' from command lineAffected if Version is earlier than 75.0.3770.80
-
Verify ANGLE library is in useThe vulnerability exists in the ANGLE graphics library (used for WebGL rendering). Check if WebGL is enabled: navigate to chrome://gpu and look for 'WebGL' in the Graphics Feature Status sectionAffected if WebGL is enabled and Chrome version is below 75.0.3770.80
-
Check Debian package version (if applicable)On Debian 10 systems, run 'dpkg -l | grep google-chrome' to see installed package versionAffected if Google Chrome package version is installed from Debian 10.0 repositories and is earlier than 75.0.3770.80
-
Check Fedora package version (if applicable)On Fedora 29 or 30, run 'rpm -qa | grep -i chrome' to see installed package versionAffected if Google Chrome package from Fedora 29 or 30 is installed and version is earlier than 75.0.3770.80
-
Check openSUSE package version (if applicable)On openSUSE Leap 15.0, 15.1, or 42.3, run 'rpm -qa | grep -i chrome' to check installed versionAffected if Google Chrome from openSUSE repositories is installed and version is earlier than 75.0.3770.80
Your environment is affected if Google Chrome (or Chromium) is installed with a version number less than 75.0.3770.80 and WebGL/ANGLE graphics functionality is enabled in the browser.
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
Upgrade Google Chrome to version 75.0.3770.80 or later, or ensure automatic browser updates are enabled and applied.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5836 — 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-5836 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