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

CVE-2024-21774

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 in some Intel(R) Processor Identification Utility software before versions 6.10.34.1129, 7.1.6 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 Processor Identification Utility contains an uncontrolled search path vulnerability (DLL hijacking) that allows the application to load malicious DLLs from locations writable by an authenticated local user, potentially leading to privilege escalation.

MitigationUpdate Intel Processor Identification Utility to version 6.10.34.1129 (Windows) or 7.1.6 (other platforms) or later to remediate this vulnerability.

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. Check if Intel Processor Identification Utility is installed
    Search for the application in common installation directories such as C:\Program Files\Intel\ or /Applications/ on macOS, or check Add/Remove Programs on Windows. Look for executables named IntelProcessorUtility.exe, IntelProcessorID.exe, or similar.
    Affected if The application is present on the system
  2. Identify the installed version
    Right-click the executable, select Properties, and check the Details tab for the File Version. On Windows, you can also run 'wmic product get name,version' or check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Intel\ProcessorIdentification or similar keys.
    Affected if The version cannot be determined or is below 6.10.34.1129 (Windows) or 7.1.6 (other platforms)
  3. Compare version against fixed releases
    Compare your identified version number to 6.10.34.1129 for Windows or 7.1.6 for other platforms. If the installed version is lower, it is within the affected range.
    Affected if Version is lower than 6.10.34.1129 on Windows or lower than 7.1.6 on other platforms
  4. Check for writable directories in application search path
    Examine the directory containing the Intel Processor Identification Utility executable and directories listed in the system PATH for world-writable or user-writable permissions. On Windows, right-click folders, go to Properties, then Security tab to check permissions.
    Affected if The application directory or any directory in its DLL search path is writable by an authenticated user

If Intel Processor Identification Utility is installed with a version below 6.10.34.1129 (Windows) or 7.1.6 (other platforms), and the application directory or PATH is writable by a local user, the system is vulnerable to DLL hijacking and privilege escalation.

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 Processor Identification Utility to version 6.10.34.1129 (Windows) or 7.1.6 (other platforms) or later to remediate this vulnerability.

Recommended fix High confidence

Intel Processor Identification Utility version 6.10.34.1129 or version 7.1.6

  1. Navigate to the official Intel website and locate the Intel Processor Identification Utility download page
  2. Download version 6.10.34.1129 or version 7.1.6 (whichever is available for your platform)
  3. Verify the downloaded installer matches the expected version
  4. Close any running instances of the Intel Processor Identification Utility
  5. Run the installer with appropriate administrative privileges
  6. Follow the on-screen installation prompts to complete the update
  7. Restart the system if prompted by the installer

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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