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

CVE-2024-34164

MEDIUM · 6.7 CVSS v3.1 Published 2024-11-13
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 element in some Intel(R) MAS software before version 2.5 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

Intel Memory and Storage Tool (MAS) before version 2.5 contains an uncontrolled search path element vulnerability, allowing an authenticated local user to manipulate the DLL search path and potentially execute arbitrary code with elevated privileges.

MitigationUpdate Intel MAS to version 2.5 or later to remediate the 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. Verify Intel MAS is installed
    Open Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for 'Intel Memory and Storage Tool' or 'Intel MAS' in the installed programs list
    Affected if Intel MAS does not appear in the installed programs list - the vulnerability does not apply
  2. Identify the installed version
    Right-click on Intel MAS in the Programs list, select Properties, and note the version number shown in the Version field; alternatively, open Intel MAS application and check Help > About for the version
    Affected if The displayed version is blank or cannot be determined - version cannot be compared
  3. Compare version against affected range
    Compare the installed version number to version 2.5. The vulnerability affects all versions before 2.5 (for example, 2.4, 2.3, 2.0, 1.x)
    Affected if The installed version is less than 2.5 (for example, 2.4.0, 2.3.1, 1.5.2) - the system is vulnerable to DLL hijacking
  4. Confirm execution context
    Check if Intel MAS is typically run with elevated privileges or is configured to run as administrator; examine the shortcut properties or service configuration if applicable
    Affected if Intel MAS runs with administrator or SYSTEM privileges and the version is below 2.5 - the arbitrary code execution aspect of the vulnerability is applicable

If Intel Memory and Storage Tool is installed and the version is below 2.5, 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Intel MAS to version 2.5 or later to remediate the vulnerability.

Recommended fix High confidence

Intel Memory and Storage (MAS) version 2.5 or later

  1. 1. Navigate to the official Intel website and locate the Intel Memory and Storage (MAS) software download page.
  2. 2. Download Intel MAS version 2.5 or later.
  3. 3. Verify the version number of the downloaded installer.
  4. 4. Run the installer with appropriate administrative privileges.
  5. 5. Follow the installation wizard prompts to complete the upgrade.
  6. 6. Restart the system if prompted by the installer.
  7. 7. Verify the installed version by checking Intel MAS version information to confirm it shows version 2.5 or later.
Caveat Unknown from available advisory information; review Intel release notes for any compatibility or feature changes before upgrading

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
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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