dbcve.org
Gpu DriverApplication · Nvidia

CVE-2013-5987

HIGH · 7.2 CVSS v2.0 Published 2014-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
No privileges 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
Unspecified vulnerability in NVIDIA graphics driver Release 331, 325, 319, 310, and 304 allows local users to bypass intended access restrictions for the GPU and gain privileges via unknown vectors.

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

NVIDIA graphics driver for Windows contains a local privilege escalation vulnerability affecting versions 304, 310, 319, 325, and 331. Local attackers can bypass intended GPU access restrictions to gain elevated privileges through unknown vectors related to GPU driver interactions.

MitigationUpdate NVIDIA graphics drivers to versions newer than the affected releases (331, 325, 319, 310, 304). Apply the latest stable driver version from NVIDIA's official download page, prioritizing systems with direct GPU 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:= 304.00= 310.00= 319.00= 325.00= 331.00
Mac Os XOperating system
Affected:= 10.9.1

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/I:C/A:C

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. Check NVIDIA driver version in Windows
    Open NVIDIA Control Panel, go to 'System Information' or right-click on Desktop and select 'NVIDIA Control Panel' > 'System Information'. Record the driver version shown (e.g., 304.00, 310.00, 319.00, 325.00, or 331.00).
    Affected if The displayed driver version exactly matches 304.xx, 310.xx, 319.xx, 325.xx, or 331.xx (these are the vulnerable versions).
  2. Verify driver version via Device Manager
    Open Device Manager, expand 'Display adapters', right-click on the NVIDIA GPU device, select 'Properties', go to the 'Driver' tab, and note the driver version string.
    Affected if The driver version shown is one of the affected versions: 304.xx, 310.xx, 319.xx, 325.xx, or 331.xx.
  3. Check NVIDIA driver version via command line
    Open Command Prompt and run 'nvidia-smi' if available, or check the registry key 'HKLM\SYSTEM\CurrentControlSet\Services\nvlddmkm\DriverVersion'.
    Affected if The version retrieved from nvidia-smi or the registry matches 304.xx, 310.xx, 319.xx, 325.xx, or 331.xx.
  4. Confirm system has NVIDIA GPU hardware
    Open Device Manager under 'Display adapters' and verify an NVIDIA GPU is present and actively installed.
    Affected if An NVIDIA GPU is installed and the associated driver version is one of the vulnerable versions listed.

A system is affected if it runs any NVIDIA graphics driver version 304.xx, 310.xx, 319.xx, 325.xx, or 331.xx on Windows with an active NVIDIA GPU.

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 NVIDIA graphics drivers to versions newer than the affected releases (331, 325, 319, 310, 304). Apply the latest stable driver version from NVIDIA's official download page, prioritizing systems with direct GPU access.

Fix this in Gpu Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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