dbcve.org
Mpi LibraryApplication · Intel

CVE-2024-28876

HIGH · 7.3 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 2021.12 / 2024.1 or later.
See remediation →
73/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) MPI Library software before version 2021.12 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 confidence

Intel MPI Library before version 2021.12 contains an uncontrolled search path vulnerability that allows an authenticated local user to manipulate the library's search path, potentially loading malicious libraries or resources and achieving privilege escalation.

MitigationUpdate Intel MPI Library to version 2021.12 or later. Review and restrict permissions on directories in the library search path to prevent user-controlled placement of malicious files.

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
Mpi LibraryApplication
Affected:< 2021.12
Oneapi Hpc ToolkitApplication
Affected:< 2024.1

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
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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. Identify Intel MPI Library installation path
    Check common installation directories such as /opt/intel/oneapi/mpi or C:\Program Files (x86)\Intel\OneAPI\mpi, and look for version information in the library's release notes or version file (often named version.txt or included in the installation metadata).
    Affected if The library is installed and the version is below 2021.12 (e.g., 2021.11, 2021.10, earlier).
  2. Retrieve Intel MPI Library version
    Run the command 'mpivars.sh -version' or 'mpivars.bat -version' from the Intel MPI installation directory, or inspect the file named 'VERSION' or 'mpi.version' in the installation root folder.
    Affected if The displayed version number is less than 2021.12.
  3. Identify Intel OneAPI HPC Toolkit installation
    Check common installation paths like /opt/intel/oneapi or C:\Program Files (x86)\Intel\OneAPI, and locate the HPC toolkit component (typically under /hpc directory).
    Affected if The HPC Toolkit is installed and its version is below 2024.1.
  4. Retrieve Intel OneAPI HPC Toolkit version
    Run 'oneapi-cli --version' or inspect the installer metadata in the OneAPI installation directory, or check the file containing the toolkit version (often in the hpc subdirectory).
    Affected if The toolkit version shown is less than 2024.1.

If Intel MPI Library version is below 2021.12 OR Intel OneAPI HPC Toolkit version is below 2024.1, the environment is affected by this uncontrolled search path vulnerability.

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 / 2024.1 or later
Fixed in 2021.122024.1
Interim mitigation

Update Intel MPI Library to version 2021.12 or later. Review and restrict permissions on directories in the library search path to prevent user-controlled placement of malicious files.

Recommended fix High confidence

Intel MPI Library 2021.12 or later; Intel oneAPI HPC Toolkit 2024.1 or later

  1. Identify the currently installed Intel(R) MPI Library version using 'mpirun --version' or checking installed programs
  2. Download Intel MPI Library version 2021.12 or later from the official Intel download center (www.intel.com)
  3. Uninstall the existing Intel MPI Library version from the system
  4. Install the downloaded Intel MPI Library 2021.12 or later version
  5. For systems with Intel oneAPI HPC Toolkit, also upgrade to version 2024.1 or later
  6. Verify the new version is installed correctly by running 'mpirun --version'
  7. Ensure the MPI library binaries are in a trusted location and not in user-controlled directories
Caveat MPI library version upgrades may require recompilation of applications compiled against the older version; verify application compatibility with the new MPI version

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

Fix this in Mpi Library Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28876 — 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-28876 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