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

CVE-2024-36291

MEDIUM · 6.7 CVSS v3.1 Published 2025-02-12
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) Chipset Software Installation Utility before version 10.1.19867.8574 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 Chipset Software Installation Utility has an uncontrolled search path vulnerability (likely DLL hijacking) that allows an authenticated local user to place malicious DLLs in the search path, potentially achieving privilege escalation to higher privileges.

MitigationUpdate Intel Chipset Software Installation Utility to version 10.1.19867.8574 or later to resolve the uncontrolled search path issue.

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 Chipset Software Installation Utility is present
    Open Programs and Features (appwiz.cpl) or check Program Files directories for an entry named 'Intel Chipset Software Installation Utility' or similar Intel chipset-related installation software.
    Affected if The utility is installed on the system.
  2. Locate the utility executable or service
    Search for files named 'IntelChipset.exe', 'IntelChipsetSetup.exe', or check Windows Services for a service related to Intel Chipset Software Installation. Common locations include Program Files/Intel or the installation directory of the utility.
    Affected if The executable or service is found on the system.
  3. Determine the installed version
    Right-click the utility executable in its installation folder, select Properties, and check the Details tab for the File Version or Product Version. Alternatively, run 'wmic product get name,version' or check the registry under HKLM\SOFTWARE\Intel for the installed version.
    Affected if The version number is lower than 10.1.19867.8574.
  4. Check if utility runs with elevated privileges
    Open Services (services.msc), locate the Intel Chipset service, right-click and select Properties, and check the 'Log On' account. Also check if the executable runs with high integrity level using Process Explorer or similar tools.
    Affected if The service runs under an administrator or System account, allowing potential privilege escalation.

If the Intel Chipset Software Installation Utility is installed with a version lower than 10.1.19867.8574 and runs with elevated privileges, the system 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Intel Chipset Software Installation Utility to version 10.1.19867.8574 or later to resolve the uncontrolled search path issue.

Recommended fix Moderate confidence

Intel(R) Chipset Software Installation Utility version 10.1.19867.8574 or later

  1. 1. Identify the current version of Intel(R) Chipset Software Installation Utility installed on the system by checking the installed program version or running the installer with version check flag
  2. 2. Navigate to Intel's official support website for chipset software or Intel Driver & Support Assistant
  3. 3. Download the latest version of Intel(R) Chipset Software Installation Utility (version 10.1.19867.8574 or later)
  4. 4. Run the installer with administrative privileges
  5. 5. Restart the system if prompted to complete the installation
Caveat Corporate environments may require testing updates in controlled environments before deployment; some chipset updates may require system restart

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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