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

CVE-2025-24923

MEDIUM · 6.7 CVSS v3.1 Published 2025-08-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 in some Intel(R) AI for Enterprise Retrieval-augmented Generation software 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

This is an untrusted search path vulnerability in Intel's Enterprise AI RAG software where the application searches for files (likely DLLs or resources) in locations that an authenticated attacker could control. By placing malicious files in these search paths, a local authenticated user can achieve privilege escalation.

MitigationApply vendor-provided patches when available; meanwhile, restrict file system permissions on directories in the application search path and ensure the software runs from controlled, non-writable directories to prevent path hijacking.

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. Locate the Intel Enterprise AI RAG installation directory
    Search the file system for directories containing 'Intel' and 'Enterprise AI' or 'RAG' in the name. Check common installation paths such as C:\Program Files\Intel or C:\Program Files (x86)\Intel on Windows, or /opt/Intel or /usr/local/Intel on Linux.
    Affected if The software is installed and the installation directory exists on the system.
  2. Identify the installed version of Intel Enterprise AI RAG
    Locate version information in the software's installation directory. Look for version.txt, about dialog, or check file properties of the main executable. On Windows, right-click the main executable and select Properties > Details. On Linux, check the binary with 'strings' or review any VERSION file in the installation directory.
    Affected if The version cannot be determined or is within an affected release range.
  3. Check directory permissions on the application installation folder
    On Windows, right-click the installation directory, select Properties > Security to verify that only trusted users have Write or Modify permissions. On Linux, run 'ls -ld <install_dir>' and review permissions. Ensure the directory is not writable by low-privilege or untrusted users.
    Affected if The installation directory or any subdirectories in the search path are writable by untrusted or low-privilege users.
  4. Examine the application search path configuration
    Review any configuration files in the installation directory for paths where the application loads DLLs, plugins, or resources. Check working directories and PATH environment variables used by the application. On Windows, use Process Monitor or similar tooling to observe file access patterns when the application starts.
    Affected if The application loads files from directories that are writable by authenticated users other than the software administrator.
  5. Verify the application runs from a controlled, non-writable location
    Confirm the software is installed and run from a protected directory such as Program Files (Windows) or /opt (Linux), not from user-writable locations like temp directories, user home folders, or network shares that allow write access.
    Affected if The software is run from or loads files out of directories that untrusted authenticated users can modify.

A user is affected if the Intel Enterprise AI RAG software is installed and the installation directory or any path in its search order is writable by authenticated attackers who could place malicious files for privilege escalation.

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 vendor-provided patches when available; meanwhile, restrict file system permissions on directories in the application search path and ensure the software runs from controlled, non-writable directories to prevent path hijacking.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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