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

CVE-2025-30506

MEDIUM · 6.7 CVSS v3.1 Published 2025-11-11
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 some Intel Driver and Support Assistant before version 25.2 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable local code execution. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires active user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

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

Intel Driver and Support Assistant before version 25.2 contains an uncontrolled search path vulnerability (DLL hijacking) that allows an unprivileged authenticated user to achieve local privilege escalation by placing malicious DLLs in a location the application searches for loads, requiring high complexity and active user interaction.

MitigationUpdate Intel Driver and Support Assistant to version 25.2 or later to remediate the uncontrolled search path vulnerability.

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. Verify Intel Driver and Support Assistant is installed
    Check for the application in Add/Remove Programs (Windows) or examine common installation directories such as C:\Program Files\Intel\Intel Driver and Support Assistant, or query the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Intel Driver and Support Assistant
    Affected if The application is present on the system
  2. Identify the installed version number
    Locate the version information through the application's About/Properties window, or check the Uninstall registry entry for the DisplayVersion value, or examine the executable file properties of IDSA.exe if found in the installation directory
    Affected if A version number cannot be determined but the software is installed
  3. Compare your version against the affected range
    Interpret the version number found and compare it to version 25.2 - note that any version below 25.2 (such as 25.1.x, 25.0.x, 24.x, etc.) falls within the vulnerable range
    Affected if The installed version is lower than 25.2 (for example: 25.1, 25.0, 24.4, 24.3, etc.)
  4. Confirm the DLL hijacking condition exists
    This vulnerability requires the application to load DLLs from locations where an unprivileged user can write files. Assess whether the application runs from a directory writable by standard users, or check if it searches paths defined by user-writable directories such as the application directory or system PATH locations
    Affected if The application loads from or searches directories writable by non-admin users and the version is below 25.2

You are affected if Intel Driver and Support Assistant is installed with any version lower than 25.2 and runs in an environment where unprivileged users can place files in directories the application searches for DLL loads.

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 Driver and Support Assistant to version 25.2 or later to remediate the uncontrolled search path vulnerability.

Recommended fix High confidence

Intel Driver and Support Assistant version 25.2

  1. Open Intel Driver and Support Assistant on the system
  2. Check the current version by clicking on the settings or about menu
  3. If the version is before 25.2, open a web browser and navigate to the official Intel website to download Intel Driver and Support Assistant version 25.2 or later
  4. Run the installer and follow the prompts to complete the update
  5. After installation, verify the version shows 25.2 or later to confirm the patch was applied

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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