dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2024-21843

MEDIUM · 6.7 CVSS v3.1 Published 2024-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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) Computing Improvement Program software before version 2.4.0.10654 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

The Intel Computing Improvement Program software before version 2.4.0.10654 has an uncontrolled search path vulnerability (DLL hijacking). An authenticated local attacker can place malicious files in a directory the software searches for executable code, allowing privilege escalation from their current user context to higher system privileges.

MitigationUpdate Intel Computing Improvement Program to version 2.4.0.10654 or later. Alternatively, restrict write access to directories in the software's search path to prevent unauthorized file placement.

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 checks

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

  1. Verify Intel Computing Improvement Program is installed
    Open Windows Settings > Apps & Features (or use 'Get-WmiObject -Class Win32_Product' in PowerShell) and search for 'Intel Computing Improvement Program' or 'IntelImprovementProgram' in the installed programs list
    Affected if The program appears in the installed programs list
  2. Determine the installed version
    Right-click the program in Apps & Features and select 'Advanced options' or check the program's entry in Add/Remove Programs. Alternatively, navigate to the program directory (typically C:\Program Files\Intel\Intel Computing Improvement Program\) and look for version information in file properties or a version.txt file
    Affected if A version number is found that is lower than 2.4.0.10654
  3. Compare version to affected range
    Document the installed version number and compare it numerically to 2.4.0.10654 (for example, 2.4.0.10653 or earlier versions are affected; 2.4.0.10654 or later are not)
    Affected if The installed version is below 2.4.0.10654 (for example, 2.4.0.10600, 2.3.5.x, etc.)
  4. Identify executable search paths used by the software
    Use Process Monitor (from Sysinternals) to monitor the Intel Computing Improvement Program process (look for process name containing 'IntelImprovementProgram' or 'IntelComputingImprovementProgram') and observe which directories it searches for DLLs or executables during startup and operation
    Affected if The software loads DLLs or executables from directories writable by non-privileged users (such as the current user's temp folder, application data directories, or the program installation directory if not protected)

A user is affected if Intel Computing Improvement Program is installed with a version lower than 2.4.0.10654 and the software searches for executable code in directories writable by the current user.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Intel Computing Improvement Program to version 2.4.0.10654 or later. Alternatively, restrict write access to directories in the software's search path to prevent unauthorized file placement.

Recommended fix Moderate confidence

Intel(R) Computing Improvement Program version 2.4.0.10654 or later

  1. Check the currently installed version of Intel(R) Computing Improvement Program on the affected system
  2. Download Intel(R) Computing Improvement Program version 2.4.0.10654 or later from Intel's official support website
  3. Run the installer with appropriate administrative privileges
  4. Follow the on-screen installation prompts to complete the update
  5. Restart the system if prompted by the installer
  6. Verify the installed version matches or exceeds 2.4.0.10654

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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