ChromeWeb browser · Google
CVE-2018-17466
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 · uneditedIncorrect texture handling in Angle in Google Chrome prior to 70.0.3538.67 allowed a remote attacker to perform an out of bounds memory read 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 confidenceAn out-of-bounds memory read vulnerability in the Angle graphics library (used by Google Chrome for WebGL rendering) allows remote attackers to read memory beyond allocated bounds through incorrect texture handling in crafted HTML pages.
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
< 70.0.3538.67
Enterprise Linux DesktopOperating system
= 6.0= 7.0
Enterprise Linux ServerOperating system
= 6.0= 7.0
Enterprise Linux Server AusOperating system
= 7.6
Enterprise Linux Server EusOperating system
= 7.6
Enterprise Linux Server TusOperating system
= 7.6
Enterprise Linux WorkstationOperating system
= 6.0= 7.0
Debian LinuxOperating system
= 8.0= 9.0CVSS 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.
-
Check if Google Chrome is installedRun 'google-chrome --version' or 'chrome --version' on Linux systems, or check Programs and Features on WindowsAffected if Chrome is not found or the command returns an error
-
Identify the installed Chrome versionExecute 'google-chrome --version' (Linux) or look in Help > About Google Chrome (GUI)Affected if The command returns a version number lower than 70.0.3538.67
-
Verify the version against affected rangeCompare the installed version string to the vulnerable range: versions prior to 70.0.3538.67 are affectedAffected if The installed version is less than 70.0.3538.67 (e.g., 69.x, 68.x, etc.)
-
Check if WebGL is enabledNavigate to chrome://settings and verify WebGL status, or inspect /etc/chromium-browser/default (Debian) or /etc/default/chromium (RHEL) for command-line flagsAffected if WebGL is enabled and the Chrome version is vulnerable (the flaw is triggered through WebGL texture handling)
A user is affected if Google Chrome is installed with a version lower than 70.0.3538.67 and WebGL rendering is enabled, allowing crafted HTML pages to trigger the out-of-bounds read in the Angle library.
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 data70.0.3538.67
Update Google Chrome to version 70.0.3538.67 or later; organizations should deploy the Chrome update via their patch management infrastructure and verify successful installation.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17466 — 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-2018-17466 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