CVE-2024-34165
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 · uneditedUncontrolled search path in some Intel(R) oneAPI DPC++/C++ Compiler 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 confidenceThe Intel oneAPI DPC++/C++ Compiler before version 2024.2 contains an uncontrolled search path vulnerability. An authenticated local attacker can exploit this by placing malicious files in a location the compiler searches for executable modules or libraries, potentially leading to privilege escalation.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Intel DPC++/C++ Compiler installationSearch typical installation directories such as /opt/intel/oneAPI (Linux) or C:\Program Files\Intel\oneAPI (Windows), and check for the 'compiler' subdirectory containing 'dpcpp' or 'icpx' executablesAffected if The compiler is found in a user-writable directory or no installation is found at all
-
Determine the installed compiler versionRun the compiler with --version or -v flag, for example: /opt/intel/oneAPI/compiler/latest/linux/bin/icpx --version or dpcpp --versionAffected if The version output shows a build date or version number earlier than 2024.2
-
Check for untrusted directories in the PATH environment variableReview the system PATH and any oneAPI initialization scripts (setvars.sh or setvars.bat) for user-writable directories such as home directories, temp folders, or network sharesAffected if Any user-writable or untrusted directory appears before the trusted compiler directory in PATH
-
Inspect library and module search pathsExamine environment variables like LIBRARY_PATH, LD_LIBRARY_PATH (Linux), or LIB (Windows) and run 'icpx -print-search-dirs' to see which directories the compiler will search for libraries and modulesAffected if User-writable directories are included in the compiler's library or module search paths
-
Verify directory permissions on the compiler installationCheck that the compiler directory and its subdirectories are owned by root or the Intel service account and are not world-writable (use 'ls -la' on Linux or check Permissions in Windows)Affected if The compiler directory or any parent directory in its search path is writable by non-privileged users
A system is affected if Intel oneAPI DPC++/C++ Compiler version 2024.1 or earlier is installed AND user-writable directories are present in the compiler's executable or library search paths.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Intel oneAPI DPC++/C++ Compiler version 2024.2 or later. Additionally, ensure the compiler is launched from trusted directories and that user-writable directories are not included in the search path.
2024.2
- Download Intel(R) oneAPI DPC++/C++ Compiler version 2024.2 or later from the official Intel website
- Verify the download integrity using provided checksums
- Install the updated compiler version following Intel's installation documentation
- Update any build scripts, CI/CD pipelines, or environment configurations that reference the compiler path to ensure they use the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34165 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-34165 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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