dbcve.org
Graphics DriverApplication · Intel

CVE-2020-0505

MEDIUM · 6.1 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 →
63/100
Remediation priority · Elevated
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
Improper conditions check in 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 information disclosure and denial of service via local

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

Improper conditions check in 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 local user to potentially enable information disclosure and denial of service. The vulnerability stems from the driver not properly validating certain conditions before performing operations, which could be exploited to read sensitive information or cause a denial of service condition.

MitigationUpdate Intel(R) Graphics Drivers to version 15.33.49.5100 or higher for legacy branches, or 26.20.100.7212 or higher for newer branches. Apply the appropriate driver version for the installed graphics hardware.

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
None
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L

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 if Intel Graphics Driver is present
    Open Device Manager, expand 'Display adapters', and look for Intel graphics devices (e.g., Intel(R) UHD Graphics, Intel(R) Iris(R) Xe, etc.). Alternatively, run 'dxdiag' and check the 'Display' tab for Intel graphics information.
    Affected if No Intel graphics device is listed - the system is not affected by this CVE.
  2. Determine the installed Intel Graphics Driver version
    In Device Manager, right-click the Intel graphics device, select 'Properties', go to the 'Driver' tab, and note the 'Driver Version' field. Alternatively, check the Windows Registry at HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318} for the 'DriverVersion' value.
    Affected if Unable to determine the driver version - further investigation required.
  3. Compare the installed version against affected ranges
    Compare the four-part version number (e.g., 15.33.x.x) to the affected ranges: 15.33.x.x to 15.33.48.x, 15.36.x.x to 15.36.37.x, 15.40.x.x to 15.40.43.x, 15.45.x.x to 15.45.29.x, or 26.20.x.x to 26.20.100.7211. For the 15.x branch, check if the version is below 15.33.49.5100, 15.36.38.5117, 15.40.44.5107, or 15.45.30.5103. For the 26.x branch, check if the version is below 26.20.100.7212.
    Affected if The installed version falls within any of the affected ranges listed above - the system is potentially vulnerable.
  4. Verify the graphics driver is loaded and active
    Confirm the Intel graphics driver is not disabled or showing a warning symbol in Device Manager. The driver must be installed and active for the vulnerability to be exploitable.
    Affected if The Intel graphics driver is disabled or not loaded - the vulnerability is not currently exploitable despite an affected version being installed.

A user is affected if they have an Intel Graphics Driver installed with a version that matches one of the vulnerable ranges (15.33.x.x to 15.33.48.x, 15.36.x.x to 15.36.37.x, 15.40.x.x to 15.40.43.x, 15.45.x.x to 15.45.29.x, or 26.20.x.x to 26.20.100.7211) and the driver is currently loaded and active on the system.

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(R) Graphics Drivers to version 15.33.49.5100 or higher for legacy branches, or 26.20.100.7212 or higher for newer branches. Apply the appropriate driver version for the installed graphics hardware.

Fix this in Graphics Driver Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-0505 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-0505 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