CVE-2024-21766
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 Math Kernel Library 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 confidenceIntel oneAPI Math Kernel Library before version 2024.1 contains an uncontrolled search path vulnerability allowing DLL/library hijacking. An authenticated local user could place malicious libraries in the search path to achieve privilege escalation when the affected software loads those libraries.
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.
-
Verify Intel oneAPI MKL installationSearch for the Intel oneAPI MKL installation directory on the system, or check Windows Registry under HKLM\SOFTWARE\Intel\OneAPI for MKL entries.Affected if Intel oneAPI MKL is present on the system
-
Identify installed versionExamine the version information of the MKL library files (such as mkl*.dll on Windows or libmkl* on Linux) or check version metadata in the installation directory.Affected if A version number for Intel oneAPI MKL can be determined
-
Compare version to fixed releaseCompare the identified version to 2024.1. If the version is lower than 2024.1, the installation is vulnerable to the uncontrolled search path flaw.Affected if The installed version is before 2024.1
-
Confirm library is loadedMonitor for processes that load the Intel oneAPI MKL libraries, or review application configurations that link against MKL.Affected if Any application loads or links against the vulnerable MKL library
The environment is affected if Intel oneAPI MKL is installed with a version lower than 2024.1 and any application loads the library.
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 Math Kernel Library to version 2024.1 or later. Audit systems for unauthorized library placement in application directories.
Intel(R) oneAPI Math Kernel Library version 2024.1
- 1. Identify the current version of Intel(R) oneAPI Math Kernel Library installed on the system
- 2. Download Intel(R) oneAPI Math Kernel Library version 2024.1 from the official Intel website or Intel Developer Catalog
- 3. Uninstall the existing version of Intel oneAPI Math Kernel Library
- 4. Install version 2024.1 using the Intel installer
- 5. Verify the installation was successful by checking the installed version matches 2024.1
- 6. Reboot the system if required by the installer
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21766 — 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-21766 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