dbcve.org
Integrated Performance PrimitivesApplication · Intel

CVE-2024-28952

MEDIUM · 6.7 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to 2021.12.0 / 2024.2 or later.
See remediation →
67/100
Remediation priority · Elevated

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 · unedited
Uncontrolled search path for some Intel(R) IPP software for Windows before version 2021.12.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 · moderate confidence

This is an uncontrolled search path vulnerability in Intel(R) Integrated Performance Primitives (IPP) library for Windows versions prior to 2021.12.0. An authenticated local user could exploit this by placing malicious DLLs in directories searched by the application, potentially achieving privilege escalation.

MitigationUpgrade Intel IPP to version 2021.12.0 or later to resolve the uncontrolled search path vulnerability.

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
Integrated Performance PrimitivesApplication
Affected:< 2021.12.0
Oneapi Base ToolkitApplication
Affected:< 2024.2

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Intel IPP installation directory
    Search for the Intel IPP library files in common installation paths: %ProgramFiles%\Intel\Intel(R) Integrated Performance Primitives, %ProgramFiles(x86)%\Intel\Intel(R) Integrated Performance Primitives, or check the system PATH for directories containing ipp*.dll files
    Affected if The directory exists and contains ipp*.dll files but the version cannot be determined or is below 2021.12.0
  2. Check Intel IPP DLL version
    Right-click on any ipp*.dll file in the identified directory, select Properties, then view the Details tab to find the File Version
    Affected if The displayed file version is less than 2021.12.0 (for example, 2021.x.x, 2020.x.x, or earlier)
  3. Locate Intel OneAPI Base Toolkit
    Search for OneAPI installation at %ProgramFiles%\Intel\oneAPI or %ProgramFiles(x86)%\Intel\oneAPI, or check Add/Remove Programs for Intel oneAPI Base Toolkit entry
    Affected if The toolkit is installed but the version shown in Add/Remove Programs or the installation directory is less than 2024.2
  4. Verify OneAPI version in registry
    Open Registry Editor and check HKLM\SOFTWARE\Intel\Intel(R) OneAPI\InstallInfo for a Version value, or check HKLM\SOFTWARE\WOW6432Node\Intel\Intel(R) OneAPI if on 64-bit Windows
    Affected if A Version value exists and is less than 2024.2.0.0 or the key is absent on systems with older OneAPI installations

You are affected if Intel IPP library version is below 2021.12.0 or Intel OneAPI Base Toolkit version is below 2024.2, as these versions contain the uncontrolled search path vulnerability allowing DLL hijacking.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2021.12.0 / 2024.2 or later
Fixed in 2021.12.02024.2
Interim mitigation

Upgrade Intel IPP to version 2021.12.0 or later to resolve the uncontrolled search path vulnerability.

Recommended fix High confidence

Intel IPP 2021.12.0 or later; OneAPI Base Toolkit 2024.2 or later

  1. Identify the currently installed version of Intel Integrated Performance Primitives (IPP) on the system
  2. Identify the currently installed version of OneAPI Base Toolkit on the system
  3. For Integrated Performance Primitives: If version is below 2021.12.0, download and install version 2021.12.0 or later from the official Intel download repository
  4. For OneAPI Base Toolkit: If version is below 2024.2, download and install version 2024.2 or later from the official Intel download repository
  5. Verify the installed versions after upgrade to confirm the patch was applied successfully
  6. Restart any applications or services that depend on the Intel IPP libraries to ensure the new version is loaded

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Integrated Performance Primitives Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28952 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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