CVE-2024-21857
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 Compiler software before version 2024.1 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 Compiler before version 2024.1 suffers from an uncontrolled search path vulnerability (DLL hijacking). An authenticated local attacker can plant malicious DLLs in directories the compiler searches when loading resources, causing arbitrary code execution with the compiler's privileges, 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 Intel oneAPI Compiler installationCheck common installation paths such as C:\Program Files\Intel\oneAPI\ or C:\Program Files (x86)\Intel\oneAPI\ on Windows, or /opt/intel/oneapi/ on Linux. Use 'where icx' or 'which icx' to find the compiler executable if it is in PATH.Affected if The compiler is found in the system
-
Identify compiler versionRun 'icx --version' or 'icpc --version' to display the Intel oneAPI C/C++ compiler version. Alternatively, check the version information of the compiler executable via file properties on Windows or 'icx --version' on Linux.Affected if The command returns a version number
-
Compare version against 2024.1Review the reported version number. Version numbers follow the pattern YYYY.N (e.g., 2023.2, 2024.0). Compare numerically: any version lower than 2024.1 is in the affected range.Affected if The reported version is earlier than 2024.1 (e.g., 2023.1, 2023.2, 2024.0)
-
Verify compiler can be invokedConfirm that the compiler can be executed by the user. Run a simple compilation command such as 'icx -v' or 'icx --help' to verify the compiler is functional and capable of loading DLLs at runtime.Affected if The compiler executes without errors
The environment is affected if Intel oneAPI Compiler is installed and the installed version is earlier than 2024.1, allowing the compiler to load DLLs from attacker-controlled directories.
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 Intel oneAPI Compiler to version 2024.1 or later which includes the fix for this vulnerability.
Intel oneAPI Compiler 2024.1
- 1. Identify the current version of Intel(R) oneAPI Compiler installed on the system
- 2. Download Intel oneAPI Compiler version 2024.1 or later from the official Intel website or repository
- 3. Uninstall the current version of the Intel oneAPI Compiler
- 4. Install the updated version 2024.1 or newer
- 5. Verify the installation completed successfully and confirm the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21857 — 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-21857 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