Graphics DriverApplication · Intel

CVE-2020-0508

HIGH · 7.8 CVSS v3.1 Published 2020-03-12
Fix available
A fix is available. Upgrade to 15.33.49.5100 / 15.36.38.5117 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Incorrect default permissions in the installer for Intel(R) Graphics Drivers before versions 15.33.49.5100, 15.36.38.5117, 15.40.44.5107, 15.45.30.5103, and 26.20.100.7212 may allow an authenticated user to potentially enable escalation of privilege 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 confidence

The Intel Graphics Drivers installer for versions prior to 15.33.49.5100, 15.36.38.5117, 15.40.44.5107, 15.45.30.5103, and 26.20.100.7212 contains incorrect default permissions that allow an authenticated local user to manipulate installer files or directories to gain elevated privileges.

MitigationUpdate Intel Graphics Drivers to version 15.33.49.5100 or higher (15.36.38.5117, 15.40.44.5107, 15.45.30.5103, 26.20.100.7212 or later) on all affected systems.

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
Graphics DriverApplication
Affected:>= 15.33, < 15.33.49.5100>= 15.36, < 15.36.38.5117>= 15.40, < 15.40.44.5107>= 15.45, < 15.45.30.5103>= 26.20, < 26.20.100.7212

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Intel Graphics Driver version
    Open Device Manager, expand Display adapters, right-click on Intel Graphics device, select Properties, go to Driver tab. Alternatively, run 'dxdiag' and check the Display tab for the driver version.
    Affected if Version falls within any of these ranges: >= 15.33 and < 15.33.49.5100; >= 15.36 and < 15.36.38.5117; >= 15.40 and < 15.40.44.5107; >= 15.45 and < 15.45.30.5103; >= 26.20 and < 26.20.100.7212
  2. Verify driver version via Windows Registry
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\igfx. Check the DriverVersion value in the right pane. Compare this value against the affected version ranges.
    Affected if The DriverVersion value is lower than 15.33.49.5100, 15.36.38.5117, 15.40.44.5107, 15.45.30.5103, or 26.20.100.7212 (depending on your driver branch)
  3. Check installer directory permissions
    Locate Intel Graphics driver installer files or temporary installation directories (commonly found in Program Files\Intel or %TEMP%\igfx). Right-click the folder, select Properties, then Security tab. Verify that standard users or authenticated users do not have Full Control or Modify permissions.
    Affected if Authenticated users or non-admin users have Full Control or Modify permissions on Intel installer directories or files

You are affected if your Intel Graphics Driver version is within any of the listed vulnerable version ranges AND the installer files/directories retain overly permissive ACLs allowing standard users to modify them.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 15.33.49.5100 / 15.36.38.5117 / 15.40.44.5107 or later
Fixed in 15.33.49.510015.36.38.511715.40.44.5107
Interim mitigation

Update Intel Graphics Drivers to version 15.33.49.5100 or higher (15.36.38.5117, 15.40.44.5107, 15.45.30.5103, 26.20.100.7212 or later) on all affected systems.

Fix this in Graphics Driver Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-0508 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-0508 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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