CVE-2018-12152
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 · uneditedPointer corruption in Unified Shader Compiler in Intel Graphics Drivers before 10.18.x.5056 (aka 15.33.x.5056), 10.18.x.5057 (aka 15.36.x.5057) and 20.19.x.5058 (aka 15.40.x.5058) may allow an unauthenticated remote user to potentially execute arbitrary WebGL code via local access.
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 confidencePointer corruption vulnerability in Intel's Unified Shader Compiler within graphics drivers allows potential arbitrary code execution via WebGL. The flaw affects multiple driver branches (15.33.x, 15.36.x, 15.40.x) prior to the specified patch versions. Local access is required for exploitation.
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= 15.33.43.4425= 15.33.45.4653= 15.33.46.4885= 15.33.47.5059= 15.36.26.4294= 15.36.28.4332= 15.36.31.4414= 15.36.33.4578= 15.36.34.4889= 15.36.35.5057= 15.40.34.4624= 15.40.36.4703CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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.
-
Identify Intel Graphics Driver versionOpen Device Manager, expand Display adapters, right-click Intel Graphics and select Properties, then view the Driver version field. Alternatively, run 'dxdiag' in the Run dialog and check the Drivers tab, or check the registry key at HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\DriverVersionAffected if The installed version matches one of these: 15.33.43.4425, 15.33.45.4653, 15.33.46.4885, 15.33.47.5059, 15.36.26.4294, 15.36.28.4332, 15.36.31.4414, 15.36.33.4578, 15.36.34.4889, 15.36.35.5057, 15.40.34.4624, or 15.40.36.4703
-
Determine driver branch familyIdentify whether your driver version belongs to the 15.33.x, 15.36.x, or 15.40.x branch family by examining the first two number groups in the version stringAffected if The driver belongs to the 15.33.x, 15.36.x, or 15.40.x branch and the full version matches an affected version listed above
-
Verify WebGL is accessibleOpen a web browser, navigate to a WebGL test page (such as webgl.org's sample viewer), or type 'about:gpu' in Chrome to view WebGL status. In Firefox, type 'about:support' and search for WebGLAffected if WebGL is enabled and functional in any installed web browser, as exploitation occurs through WebGL content
You are affected if your Intel Graphics Driver version matches one of the twelve specific versions listed in the affected products, your driver belongs to the 15.33.x, 15.36.x, or 15.40.x branch, and WebGL is enabled in your environment.
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 dataUpdate Intel Graphics Drivers to version 10.18.x.5056 (15.33.x), 10.18.x.5057 (15.36.x), or 20.19.x.5058 (15.40.x) or later, depending on the installed driver branch.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12152 — 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-12152 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