dbcve.org
Gpu DriverApplication · Nvidia

CVE-2017-0317

HIGH · 7.5 CVSS v3.0 Published 2017-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High

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
All versions of NVIDIA GPU and GeForce Experience installer contain a vulnerability where it fails to set proper permissions on the package extraction path thus allowing a non-privileged user to tamper with the extracted files, potentially leading to escalation of privileges via code execution.

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 NVIDIA GPU driver and GeForce Experience installer fails to set proper permissions on the package extraction path during installation. This allows a non-privileged user to tamper with or replace extracted files before they are executed with elevated privileges, resulting in local privilege escalation through arbitrary code execution.

MitigationApply the NVIDIA security update that addresses this vulnerability. As a temporary mitigation, ensure only trusted administrative users are present on the system during driver installation and avoid installing in multi-user environments where untrusted users have physical or logical access.

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
Gpu DriverApplication
Affected:all versions

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
High
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:C/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. Verify NVIDIA GPU driver is installed
    Open Control Panel > Programs and Features, or run 'wmic product get name,version' and look for NVIDIA-related entries such as 'NVIDIA GeForce Experience' or 'NVIDIA Graphics Driver'. Alternatively, check Device Manager for NVIDIA display adapters.
    Affected if NVIDIA GPU driver or GeForce Experience installer is present on the system
  2. Identify driver extraction paths
    Check common temporary locations used by NVIDIA installers during extraction. Look for folders containing 'NVIDIA' or 'nv' in their name within user-accessible temp directories such as %TEMP%, %LOCALAPPDATA%\Temp, or C:\ProgramData\. Inspect folder properties to view permissions.
    Affected if Extraction folders exist and are accessible to non-privileged users (permissions show Users or Everyone with Write/modify access)
  3. Check for recent NVIDIA installer activity
    Review Windows Event Logs under Application and System logs for MSI installer events from NVIDIA, or check the Windows Installer folder at C:\Windows\Temp for recently created NVIDIA-related folders. Use 'msiexec /x' or check Add/Remove Programs for recent installation timestamps.
    Affected if A recent NVIDIA driver installation has occurred and the extraction path remains accessible to standard users
  4. Assess multi-user environment access
    Determine if the system has multiple user accounts, particularly non-administrative or untrusted accounts. Use 'net user' or Computer Management > Local Users and Groups to enumerate accounts. Check if untrusted users have physical or remote access to the machine.
    Affected if Multiple user accounts exist and the system allows untrusted or non-administrative users to access it during or after driver installation

If an NVIDIA GPU driver is installed and the extraction path used during installation is accessible to non-privileged users, the system is vulnerable to local privilege escalation through file tampering.

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

Apply the NVIDIA security update that addresses this vulnerability. As a temporary mitigation, ensure only trusted administrative users are present on the system during driver installation and avoid installing in multi-user environments where untrusted users have physical or logical access.

Fix this in Gpu Driver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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