CVE-2019-5684
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 · uneditedNVIDIA Windows GPU Display Driver (all versions) contains a vulnerability in DirectX drivers, in which a specially crafted shader can cause an out of bounds access of an input texture array, which may lead to denial of service or 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 confidenceNVIDIA Windows GPU Display Driver contains an out-of-bounds access vulnerability in DirectX drivers where a specially crafted shader can read beyond the bounds of an input texture array, potentially leading to denial of service or arbitrary code execution.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify NVIDIA GPU hardware in systemOpen Device Manager, expand 'Display adapters', and look for NVIDIA GPU entries (e.g., NVIDIA GeForce GTX series, Quadro, etc.). Alternatively, run 'nvidia-smi' from command prompt if NVIDIA driver is installed.Affected if No NVIDIA GPU found means not affected; any NVIDIA GPU present means the driver component exists on the system.
-
Check installed NVIDIA Windows driver versionRight-click the NVIDIA GPU in Device Manager, select Properties, go to the Driver tab, and note the Driver Version string. Alternatively, open NVIDIA Control Panel and check System Information, or run 'nvidia-smi' which displays Driver Version in the output.Affected if Any installed NVIDIA Windows GPU driver version indicates the DirectX driver component is present. Per the CVE, all versions are affected.
-
Confirm DirectX usage with NVIDIA driverCheck if applications or processes using DirectX are running, or verify DirectX is available by running 'dxdiag' command which displays DirectX version and notes the display driver provider.Affected if DirectX is enabled or in use with the NVIDIA driver. The vulnerability is in the DirectX driver component, so any DirectX shader processing with the NVIDIA driver triggers the affected code path.
If the system has any NVIDIA GPU with a Windows display driver installed and DirectX is active, the environment is affected since all driver versions contain the vulnerability in the DirectX driver component.
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 NVIDIA driver update/patch for this vulnerability. In enterprise environments, test driver compatibility before broad deployment to production systems.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5684 — 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-2019-5684 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