CVE-2017-0347
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 · uneditedAll versions of the NVIDIA Windows GPU Display Driver contain a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgkDdiEscape where a value passed from a user to the driver is not correctly validated and used as the index to an array, which may lead to denial of service or potential escalation of privileges.
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 confidenceThis is an array index validation vulnerability in NVIDIA's Windows GPU kernel-mode driver (nvlddmkm.sys). The DxgkDdiEscape handler fails to properly validate a user-supplied value before using it as an array index, which could allow a local attacker to trigger an out-of-bounds access leading to denial of service or privilege escalation.
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 dataall versionsCVSS 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.
-
Confirm NVIDIA GPU driver presenceOpen Device Manager, expand 'Display adapters', and verify an NVIDIA GPU is listed. Alternatively, run 'driverquery /v | findstr nvlddmkm' or check C:\Windows\System32\drivers\nvlddmkm.sys existence.Affected if No NVIDIA GPU or nvlddmkm.sys driver is found, the system is not affected.
-
Verify driver is the Windows kernel-mode variantRight-click the NVIDIA driver in Device Manager, select Properties, then the Driver tab. Confirm the driver file is nvlddmkm.sys (the Windows kernel-mode driver).Affected if The driver is not nvlddmkm.sys (for example, a macOS or Linux driver), this specific CVE does not apply.
-
Retrieve installed driver versionRight-click nvlddmkm.sys in C:\Windows\System32\drivers\, select Properties, then the Details tab to view File Version. Or use PowerShell: 'Get-ItemProperty C:\Windows\System32\drivers\nvlddmkm.sys | Select-Object -ExpandProperty VersionInfo'.Affected if Per the vendor advisory, all driver versions prior to the patched release are affected. Compare your version against NVIDIA's security bulletin.
-
Check for recent driver updatesOpen NVIDIA GeForce Experience, go to Drivers tab, and check if 'Updates' shows 'You're up to date'. Or run 'nvidia-smi' and note the driver version in the output.Affected if The driver has not been updated to a version that includes the CVE-2017-0347 patch, the system remains affected.
If NVIDIA's nvlddmkm.sys Windows kernel-mode driver is installed and the version predates the vendor security patch, the environment is affected by this CVE.
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 dataApply the vendor-supplied patched NVIDIA display driver update. Prioritize systems with local user access or high availability requirements given the potential for denial of service and privilege escalation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0347 — 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-2017-0347 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