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

CVE-2025-20108

MEDIUM · 6.7 CVSS v3.1 Published 2025-05-13
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 element for some Intel(R) Network Adapter Driver installers for Windows 11 before version 29.4 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 · high confidence

This is a DLL/search path hijacking vulnerability in Intel Network Adapter Driver installers for Windows 11 prior to version 29.4. An authenticated local user can place malicious code in an uncontrolled search path used by the installer, potentially achieving privilege escalation when the installer runs.

MitigationUpdate Intel Network Adapter Driver for Windows 11 to version 29.4 or later. In enterprise environments, test the update in a controlled pilot group before broad deployment to ensure network connectivity and compatibility.

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 Windows 11 is in use
    Run 'winver' or check System Properties to verify the Windows version is 11.x
    Affected if Running Windows 11; this vulnerability specifically affects Windows 11 installer behavior
  2. Identify Intel Network Adapter Driver installation
    Open Device Manager, expand 'Network adapters', and look for Intel network adapter entries. Alternatively, open Programs and Features and search for Intel Network Adapter Driver software.
    Affected if Intel Network Adapter Driver is installed; without this product, the CVE does not apply
  3. Check installed Intel Network Adapter Driver version
    In Device Manager, right-click the Intel network adapter, select Properties, and view the Driver Version on the Driver tab. Alternatively, in Programs and Features, find the Intel Network Adapter Driver entry and note the version column.
    Affected if Version is earlier than 29.4; versions prior to 29.4 on Windows 11 contain the vulnerable installer code
  4. Audit for legacy installer files
    Search system directories (download folders, temp directories, C:\Program Files\Intel\ or similar driver update folders) for old Intel Network Adapter Driver installer executables (commonly named PROSet.exe or similar naming patterns).
    Affected if Older installer binaries (prior to version 29.4) are present on the system, as the DLL hijacking occurs during installer execution

A system is affected if it runs Windows 11 with Intel Network Adapter Driver version earlier than 29.4, or has legacy installer files from versions before 29.4 present on disk.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Intel Network Adapter Driver for Windows 11 to version 29.4 or later. In enterprise environments, test the update in a controlled pilot group before broad deployment to ensure network connectivity and compatibility.

Recommended fix High confidence

Intel Network Adapter Driver for Windows 11 version 29.4 or later

  1. Open Device Manager and locate the Intel(R) Network Adapter under Network adapters to view the current driver version.
  2. Download the latest Intel Network Adapter Driver for Windows 11 from the official Intel Support website (search for Intel Network Adapter Driver Windows 11).
  3. Verify that the downloaded installer version is 29.4 or later.
  4. Run the installer as Administrator and follow the on-screen instructions to update the driver.
  5. Restart the computer when prompted to complete the installation.
  6. After reboot, confirm the driver version is 29.4 or later in Device Manager.
Caveat No documented breaking changes; driver update may temporarily interrupt network connectivity.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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