CVE-2024-38387
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 · uneditedUncontrolled search path in the Intel(R) Graphics Driver installers for versions 15.40 and 15.45 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 confidenceThe Intel Graphics Driver installers for versions 15.40 and 15.45 contain an uncontrolled search path element (likely DLL hijacking). An authenticated local user could place malicious files in the installer search path, causing arbitrary code execution with elevated privileges during the installation process.
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 installed Intel Graphics Driver versionOpen Windows Device Manager, expand 'Display adapters', right-click on Intel graphics device, select 'Properties', go to 'Driver' tab. Alternatively, run 'msinfo32' and check the 'System Summary' for Intel graphics driver version.Affected if The displayed driver version is 15.40.x.x or 15.45.x.x
-
Check for Intel Graphics Driver installer files on systemSearch for installer files using: dir /s /b C:\*.exe 2>nul | findstr /i "intel.*graphics.*driver" or use Windows Search to locate files named similarly to Intel graphics driver installers.Affected if Installer executable files matching version 15.40 or 15.45 are found on the system
-
Verify Windows installer cache for affected versionsCheck the Windows Installer cache at C:\Windows\Installer for .msi files. Use PowerShell: Get-ChildItem -Path C:\Windows\Installer -Recurse -Filter "*.msi" | Select-Object Name, Length, LastWriteTime. Look for entries referencing Intel graphics drivers.Affected if Cached installer files for Intel Graphics Driver versions 15.40 or 15.45 are present
-
Check installation directory for DLL files placed before driver installationIf Intel Graphics Driver was recently installed or if installer files remain in a temporary directory (typically C:\Intel\Download or user temp folders), examine the directory for unexpected DLL files that could have been loaded during installation.Affected if Unexpected or suspicious DLL files exist in directories where Intel Graphics Driver installers were run
Your environment is affected if Intel Graphics Driver version 15.40.x.x or 15.45.x.x is currently installed OR if installer packages for these versions exist on the system, as both scenarios allow the uncontrolled search path vulnerability to be exploited during installation.
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 dataObtain Intel Graphics Driver installers only from official Intel channels and verify file integrity before use; apply vendor patches when released by Intel.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38387 — 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-38387 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