CVE-2024-31073
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 Level Zero 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 confidenceIntel oneAPI Level Zero software contains an uncontrolled search path vulnerability allowing DLL hijacking or similar library injection. An authenticated local attacker can place malicious libraries in the search path, causing the software to load them with elevated privileges and achieve 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.
-
Detect Intel oneAPI Level Zero installationCheck common installation paths: C:\Program Files\Intel\oneAPI\ on Windows or /opt/intel/oneapi/ on Linux. Also check Program Files (x86) and the user's home directory for oneAPI installations.Affected if Intel oneAPI Level Zero software is found installed on the system
-
Identify the installed versionLook for version information in the installation directory, check uninstall registry entries on Windows, or examine the version string in the main executable or DLL files (often named libze_loader.dll or similar).Affected if The installed version matches any vulnerable version range for CVE-2024-31073 (compare against Intel security advisories)
-
Check oneAPI directory permissionsInspect file system permissions on the Intel oneAPI installation directories. Use 'icacls' on Windows or 'ls -la' on Linux to list ACLs.Affected if Any oneAPI directory or subdirectory is writable by standard users or non-privileged accounts
-
Check PATH environment variableReview the system and user PATH variables for oneAPI entries. Run 'echo %PATH%' on Windows or 'echo $PATH' on Linux and identify any paths pointing to oneAPI directories.Affected if OneAPI paths in PATH are writable by low-privilege users or contain directories with weak permissions
-
Verify application directory is not writable by untrusted usersCheck the working directory from which oneAPI Level Zero applications typically run. Identify if that directory allows write access from low-privilege users.Affected if The working directory or any accessible oneAPI path allows authenticated local attackers to place malicious libraries
The environment is affected if Intel oneAPI Level Zero is installed and any of its directories or search paths are writable by authenticated local users who could place malicious DLLs for privilege escalation.
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.
From vendor dataApply the Intel software update for CVE-2024-31073. If immediate patching is not possible, ensure the application directory and PATH locations are not writable by low-privilege users.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31073 — 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-31073 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