CVE-2024-28954
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 · uneditedIncorrect default permissions for some Intel(R) Graphics Driver installers may allow an authenticated user to potentially enable escalation of privilege via local access.
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 confidenceIntel Graphics Driver installers ship with incorrect default file system permissions that allow authenticated local users to modify driver files or related components, potentially enabling privilege escalation to higher integrity levels.
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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/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 Intel Graphics Driver installationCheck common installation paths for Intel Graphics Drivers: %ProgramFiles%\Intel\Graphics for 64-bit or %ProgramFiles(x86)%\Intel\Graphics for 32-bit. Also check %SystemRoot%\System32\DriverStore\FileRepository\igdlh*.inf for driver store entries.Affected if Intel Graphics Driver directories exist on the system
-
Determine installed Intel Graphics Driver versionOpen Device Manager, expand Display adapters, right-click Intel Graphics entry, select Properties, go to Driver tab. Record the Driver Version. Alternatively, run 'wmic path win32_VideoController get name,driverversion' in command prompt.Affected if Driver version is within the range containing the vulnerability (check Intel security advisory for specific affected versions)
-
Inspect file permissions on driver directoriesRight-click the Intel Graphics driver folder, select Properties, go to Security tab. Click Advanced. Verify the permissions for Users and Authenticated Users groups. Check if these groups have Write or Modify permissions.Affected if Users or Authenticated Users have Write, Modify, or Full Control permissions on driver directories or subfolders
-
Check driver file ACLs for world-writable accessRun 'icacls "%ProgramFiles%\Intel" /T' or 'icacls "%SystemRoot%\System32\DriverStore\FileRepository\igdlh*" /T' in administrator command prompt. Examine output for entries granting write access to standard users.Affected if Standard user accounts have permissions to write or modify driver files or related components
The system is affected if Intel Graphics Drivers are installed and the driver directories or files have permissive ACLs that allow authenticated local users to modify driver components, which could enable privilege escalation.
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 dataDeploy Intel-provided updated graphics driver installers that correct the permission settings, and verify that installed drivers maintain proper ACLs.
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28954 — 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-28954 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