dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2024-47006

MEDIUM · 6.7 CVSS v3.1 Published 2025-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated

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
Uncontrolled search path for the Intel(R) RealSense D400 Series Universal Windows Platform (UWP) Driver for Windows(R) 10 all versions 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 confidence

The Intel RealSense D400 Series UWP driver for Windows 10 contains an uncontrolled search path vulnerability allowing DLL hijacking. An authenticated local attacker can place a malicious DLL in a directory searched by the driver, causing privilege escalation when the driver loads the trojaned library.

MitigationApply the vendor-provided driver update from Intel when available. Until then, restrict write access to directories in the driver's search path to prevent unauthorized DLL injection.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Intel RealSense D400 Series driver installation
    Open Device Manager, expand 'Cameras' or 'Imaging Devices', look for Intel RealSense D400 series devices such as D415, D435, D455. Alternatively, check Programs and Features for Intel RealSense software.
    Affected if The RealSense D400 series camera or its driver appears in the system
  2. Identify driver version
    Right-click the RealSense device in Device Manager, select Properties, go to the Driver tab, and note the Driver Version. Compare this version against any available driver updates from Intel.
    Affected if Driver version is older than the latest available from Intel
  3. Locate driver DLL search paths
    Use Sysinternals Process Monitor or examine the driver's manifest/service configuration to identify directories the UWP driver searches for DLLs. Common paths include the driver install directory, System32, and the application's working directory.
    Affected if The driver loads DLLs from directories with weak access controls
  4. Check write permissions on driver search paths
    Right-click each directory identified in step 3, select Properties, go to the Security tab, and verify which users have Write or Create Files permissions. Use icacls from an elevated command prompt for detailed ACL inspection.
    Affected if Authenticated users can write to any directory in the driver's DLL search path
  5. Verify driver binary integrity
    Use sigverif.exe or Get-AuthenticodeSignature PowerShell cmdlet to check if driver DLLs in the install directory are digitally signed by Intel. Compare file hashes against known-good values if available.
    Affected if Driver DLLs are unsigned or have been modified from their original state
  6. Audit recent DLL injection attempts
    Review Windows Event Logs under Application and Security logs for events related to DLL load failures, unexpected driver loads, or privilege escalation. Use Process Monitor to capture current DLL load activity from the RealSense driver.
    Affected if Unrecognized DLLs appear in driver load events or suspicious entries exist in event logs

A user is affected if the Intel RealSense D400 Series UWP driver is installed and any directory in its DLL search path permits write access to authenticated local users, allowing potential privilege escalation via DLL hijacking.

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

Apply the vendor-provided driver update from Intel when available. Until then, restrict write access to directories in the driver's search path to prevent unauthorized DLL injection.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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