CVE-2024-47795
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 for some Intel(R) oneAPI DPC++/C++ Compiler software before version 2025.0.0 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 confidenceThis is an uncontrolled search path vulnerability in Intel oneAPI DPC++/C++ Compiler versions prior to 2025.0.0. The compiler searches for required files in locations that may be controlled by an authenticated local user, allowing placement of malicious files that get executed with elevated privileges during compilation operations, enabling local 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.
-
Identify Intel oneAPI DPC++/C++ Compiler installation and versionRun 'where icx' or 'which icx' on Windows/Linux respectively to locate the compiler binary, then run 'icx --version' to obtain the exact version number. On Windows, also check the Intel oneAPI installation directory (typically C:\Program Files (x86)\Intel\oneAPI\) for the compiler version.Affected if The installed version is found to be earlier than 2025.0.0 (for example, 2024.x, 2023.x, or any version number less than 2025.0.0).
-
Verify user-writeable directories in compiler search pathsInspect the compiler's default include and library search paths by running 'icx -v' or reviewing environment variables such as CPATH, LIBRARY_PATH, and ONEAPI_ROOT. Identify directories that are writable by non-privileged users.Affected if Any directory in the compiler's search path (particularly include/lib folders under ONEAPI_ROOT) is writable by untrusted authenticated users, allowing them to place malicious files.
-
Check temp and working directory permissions for compilation workflowsReview file system permissions on directories commonly used during compilation (such as %TEMP% on Windows, /tmp on Linux, and project build directories). Use 'icacls' on Windows or 'ls -ld' on Linux to verify write permissions.Affected if Temp directories or project build directories are writable by untrusted users, enabling them to inject malicious files that the compiler may execute during the build process.
You are affected if Intel oneAPI DPC++/C++ Compiler version is earlier than 2025.0.0 AND any compiler search path or temp directory used during compilation is writable by untrusted authenticated users.
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 · scopedUpdate Intel oneAPI DPC++/C++ Compiler to version 2025.0.0 or later. Review and harden file system permissions on compilation directories to prevent unauthorized file placement.
2025.0.0
- Check current Intel oneAPI DPC++/C++ Compiler version using 'oneapi-cli' or checking installed programs
- Download Intel oneAPI Toolkit version 2025.0.0 or later from the official Intel website (intel.com)
- Run the installer with administrator privileges
- Follow the installation wizard to complete the update
- Verify the installed version is 2025.0.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47795 — 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-47795 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