CVE-2024-0118
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 GPU Display Driver for Windows contains a vulnerability in the user mode layer, where an unprivileged regular user can cause an out-of-bounds read. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.
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 confidenceNVIDIA GPU Display Driver for Windows contains an out-of-bounds read vulnerability in the user mode layer that can be exploited by an unprivileged regular user. Successful exploitation might lead to code execution, denial of service, privilege escalation, information disclosure, or data tampering.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Identify NVIDIA GPU hardwareOpen Device Manager, expand 'Display adapters', and check for any NVIDIA GPU listed (e.g., NVIDIA GeForce RTX series, NVIDIA Quadro, etc.)Affected if No NVIDIA GPU is present - the system is not affected. If NVIDIA GPU exists, proceed to next check.
-
Check NVIDIA Display Driver installationOpen Device Manager, right-click on the NVIDIA GPU device, select 'Properties', go to the 'Driver' tab, and note the driver version and driver dateAffected if If no NVIDIA display driver is installed or the driver version shows as 'Not available', the system is not affected. If a driver is installed, proceed to next check.
-
Obtain precise driver version numberOpen Windows PowerShell or Command Prompt and run: nvidia-smi --query-gpu="driver_version" --format=csv,noheader (requires nvidia-smi to be installed with the driver)Affected if If nvidia-smi is not available, use Device Manager driver details as an alternative source for version information.
-
Compare against fixed versionConsult NVIDIA's official security bulletin for CVE-2024-0118 to obtain the specific fixed driver version, then compare your installed version from step 3 against itAffected if If the installed driver version is lower than the fixed version listed in NVIDIA's security bulletin, the system is potentially affected by this vulnerability.
A system is affected if it has an NVIDIA GPU running a display driver version lower than the fixed version specified in NVIDIA's security bulletin for CVE-2024-0118.
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 latest NVIDIA GPU Display Driver update for Windows. Check NVIDIA's security bulletin for the specific fixed version and deploy via standard IT patch management processes.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0118 — 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-2024-0118 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