dbcve.org
Graphics DriverApplication · Intel

CVE-2017-5692

MEDIUM · 5.5 CVSS v3.0 Published 2018-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/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
Out-of-bounds read condition in older versions of some Intel Graphics Driver for Windows code branches allows local users to perform a denial of service attack.

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 · moderate confidence

An out-of-bounds read vulnerability in older versions of Intel Graphics Driver for Windows allows a local authenticated user to read memory outside intended boundaries, potentially causing a denial of service condition through system instability or crash.

MitigationUpdate Intel Graphics Driver for Windows to a patched version that addresses the vulnerability. Organizations should inventory affected systems and deploy the updated driver through their standard patch management process.

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.36.19.64.4170= 15.36.19.4170= 15.36.21.64.4223= 15.36.21.4222= 15.36.23.64.4251= 15.36.23.4251= 15.36.24.64.4264= 15.36.24.4264= 15.36.26.4294= 15.36.28.4332= 15.36.29.64.4371= 15.36.31.4414

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Locate Intel Graphics Driver on the system
    Open Device Manager, expand 'Display adapters', and look for Intel graphics devices (e.g., Intel HD Graphics, Intel UHD Graphics, Intel Iris). Alternatively, search for 'igfx' in driver files under C:\Windows\System32\drivers.
    Affected if No Intel graphics device is found in Device Manager - the system is not using an affected Intel Graphics Driver.
  2. Retrieve the installed 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, run 'driverquery /v | findstr -i igfx' from an elevated command prompt.
    Affected if Unable to retrieve a driver version - the Intel Graphics Driver may not be properly installed.
  3. Compare the driver version to the affected list
    Match the retrieved driver version exactly against these CVE-affected versions: 15.36.19.64.4170, 15.36.19.4170, 15.36.21.64.4223, 15.36.21.4222, 15.36.23.64.4251, 15.36.23.4251, 15.36.24.64.4264, 15.36.24.4264, 15.36.26.4294, 15.36.28.4332, 15.36.29.64.4371, 15.36.31.4414.
    Affected if The installed version matches one of the listed versions exactly - the system is running a vulnerable driver.
  4. Confirm the graphics driver is loaded and active
    Verify the driver is not disabled: in Device Manager, ensure the Intel graphics device shows 'This device is working properly' under Device Status, and the driver is not grayed out or marked as disabled.
    Affected if The driver is disabled or not loaded - the specific exploitation vector through the active graphics driver is not present.

The system is affected if it has an Intel Graphics Driver for Windows installed with a version matching one of the twelve listed affected versions and the driver is active/loaded.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Intel Graphics Driver for Windows to a patched version that addresses the vulnerability. Organizations should inventory affected systems and deploy the updated driver through their standard patch management process.

Fix this in Graphics Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5692 — 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-2017-5692 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