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

CVE-2024-39365

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 FPGA Support Package for the Intel(R) oneAPI DPC++/C++ Compiler software for Windows before version 2024.2 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

The FPGA Support Package for Intel oneAPI DPC++/C++ Compiler on Windows before version 2024.2 uses an uncontrolled search path when loading DLLs, allowing an authenticated local user to place malicious DLLs in the search path and achieve privilege escalation.

MitigationUpgrade Intel oneAPI DPC++/C++ Compiler to version 2024.2 or later, which contains the vendor fix for this 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. Locate Intel oneAPI DPC++/C++ Compiler installation
    Open Command Prompt or PowerShell and search for the compiler executable (typically icx.exe or icpx.exe). Common installation paths include C:\Program Files\Intel\oneAPI\ or C:\Program Files (x86)\Intel\oneAPI\. Run: where icx.exe 2>nul or dir /s /b "C:\Program Files*\Intel\oneAPI\icx.exe"
    Affected if The compiler executable is found in any version before 2024.2
  2. Determine installed compiler version
    Run the compiler with version flag: icx --version or icpx --version. Alternatively, right-click icx.exe in File Explorer, select Properties, and check the Details tab for Product Version or File Version.
    Affected if The displayed version number is lower than 2024.2 (for example, 2024.0, 2023.x, or any 2024.1.x variant)
  3. Confirm FPGA Support Package is present
    Check for FPGA-related components in the oneAPI installation directory. Look for folders named 'fpga' or 'compiler' within the oneAPI directory structure. The vulnerability applies specifically when FPGA support is installed. Run: dir /s /b "*fpga*" within the oneAPI folder
    Affected if FPGA support directories exist and the compiler version is before 2024.2
  4. Verify Windows is the operating system
    Confirm the system is running Windows, as this DLL hijacking vulnerability only affects the Windows platform. Run: systeminfo | findstr /B /C:"OS Name"
    Affected if Running Windows with Intel oneAPI Compiler version before 2024.2

A user is affected if Intel oneAPI DPC++/C++ Compiler for Windows is installed at a version lower than 2024.2 and includes FPGA support components, allowing a local authenticated attacker to place malicious DLLs in the compiler's search path.

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

Upgrade Intel oneAPI DPC++/C++ Compiler to version 2024.2 or later, which contains the vendor fix for this vulnerability.

Recommended fix Moderate confidence

2024.2 or later

  1. Verify the current version of Intel oneAPI DPC++/C++ Compiler installed on the system
  2. Download Intel oneAPI DPC++/C++ Compiler version 2024.2 or later from the official Intel website or through your existing Intel installation mechanism
  3. Install the updated version following standard Intel oneAPI installation procedures
  4. Verify the FPGA Support Package is updated to the fixed version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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