CVE-2024-21784
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) IPP Cryptography software before version 2021.11 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 IPP Cryptography library before version 2021.11 contains an uncontrolled search path vulnerability (DLL hijacking). The software loads dynamic-link libraries from locations that an unprivileged authenticated user can modify, potentially allowing execution of malicious code with elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2021.11.0< 2024.1CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 IPP Cryptography versionOpen Windows Control Panel > Programs and Features, or use 'wmic product get name,version' command, and locate 'Intel IPP Cryptography' or 'Intel Integrated Performance Primitives Cryptography' entryAffected if The installed version is lower than 2021.11.0
-
Identify Intel OneAPI Base Toolkit versionOpen Windows Control Panel > Programs and Features, or use 'wmic product get name,version' command, and locate 'Intel OneAPI Base Toolkit' entryAffected if The installed version is lower than 2024.1
-
Verify DLL search path usageUse Process Monitor or examine application logs to observe if the Intel IPP Cryptography library loads DLLs from user-writable directories such as the application working directory or directories in the system PATHAffected if The library loads unsigned or untrusted DLLs from locations writable by non-privileged users, enabling potential DLL hijacking
Your environment is affected if Intel IPP Cryptography is installed below version 2021.11.0 OR Intel OneAPI Base Toolkit is below version 2024.1, and these libraries load DLLs from user-modifiable 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 · scoped2021.11.02024.1
Update Intel IPP Cryptography software to version 2021.11 or later to obtain the vendor patch that secures the DLL search path.
Intel IPP Cryptography version 2021.11.0 or later; Intel OneAPI Base Toolkit version 2024.1 or later
- 1. Identify which Intel IPP Cryptography or OneAPI Base Toolkit products are installed on the system
- 2. Check the current version of the installed software using 'ippcp --version' or checking the product installation directory
- 3. Download the fixed version of Intel IPP Cryptography (2021.11.0 or later) from the official Intel website at software.intel.com
- 4. Download the fixed version of Intel OneAPI Base Toolkit (2024.1 or later) if that product is also installed
- 5. Apply the update following Intel's installation documentation, ensuring to run as administrator
- 6. Verify the updated version is correctly installed after the update completes
- 7. Restart any applications that use the IPP Cryptography library to ensure the updated DLLs are loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing4.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,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21784 — 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-21784 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