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

CVE-2024-34167

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 for the Intel(R) Server Board S2600ST Family BIOS and Firmware Update software all versions 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 Server Board S2600ST Family BIOS and Firmware Update software suffers from an uncontrolled search path vulnerability (likely DLL hijacking) where an authenticated local attacker can place malicious code in a searched directory, causing it to execute with elevated privileges when the software runs.

MitigationApply vendor-provided firmware updates when available; until then, restrict write access to directories in the software's search path and ensure the update utility runs from trusted, controlled locations only.

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. Identify if the system is an Intel Server Board S2600ST
    Run 'dmidecode -s baseboard-manufacturer' and 'dmidecode -s baseboard-product-name' to confirm the system model
    Affected if The system is not an Intel Server Board S2600ST family product (vulnerability does not apply)
  2. Locate the Intel BIOS and Firmware Update utility
    Search for Intel update executables such as 'BIOSUpdate.exe', 'fwupdx64.exe', 'IntelUpdate.exe', or similar in standard Intel installation directories (commonly C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\). Use 'dir /s C:\Program Files\Intel\*.exe' or 'find /usr -name '*Intel*' on Linux-based management tooling
    Affected if The Intel Server Board S2600ST BIOS/Firmware Update utility is not installed (vulnerability does not apply)
  3. Determine the installed firmware update utility version
    Right-click the located executable, select Properties, then view the Details tab for version information. Alternatively, run '<utilityname>.exe /version' or 'wmic datafile where "name='C:\\path\\to\\utility.exe'" get Version'
    Affected if The version cannot be determined or is older than vendor-provided patched versions (compare against Intel's official security advisory for CVE-2024-34167)
  4. Check write permissions on the utility's directory and search path locations
    Right-click the folder containing the update utility, select Properties, then Security tab to review write permissions. Use 'icacls C:\path\to\utility' or on Linux 'ls -la /path/to/utility'
    Affected if Untrusted or low-privileged users (such as standard user accounts) have Write or Create Files permissions in directories the utility searches for DLLs or executables
  5. Verify the utility executes with elevated privileges
    Right-click the update utility executable, select Properties, then Compatibility tab to check 'Run as administrator' setting. Also check if the utility is invoked via scheduled task with elevated rights using 'schtasks /query /tn "IntelUpdate"'
    Affected if The firmware update utility is configured to run with administrator or system-level privileges (the malicious code would execute at that elevated level)

A user is affected if they are running the Intel Server Board S2600ST BIOS/Firmware Update utility on an S2600ST system, the utility has an older unpatched version, and untrusted local users have write access to directories in the utility's search path where they could place malicious DLLs or executables.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided firmware updates when available; until then, restrict write access to directories in the software's search path and ensure the update utility runs from trusted, controlled locations only.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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