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

CVE-2024-42492

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

NVD · unedited

Uncontrolled search path element in some BIOS and System Firmware Update Package for Intel(R) Server M50FCP family before version R01.02.0002 may allow a privileged user to potentially enable escalation of privilege via local access.

Technical summary

dbcve analysis · high confidence

This is an uncontrolled search path element vulnerability in Intel Server M50FCP family BIOS and System Firmware Update Package. The vulnerability allows a privileged local user to potentially escalate privileges by exploiting how the firmware update process searches for and loads executable components from untrusted locations.

MitigationApply Intel firmware update R01.02.0002 or later to the affected Intel Server M50FCP family systems. This is a vendor-supplied patch that addresses the uncontrolled search path vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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?

dbcve checks

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

Identify system model

Run command 'dmidecode -s system-product-name' or check system BIOS information screen to verify the hardware is Intel Server M50FCP family

Affected if The system product name does not contain 'M50FCP' - not affected
Check BIOS firmware version

Run command 'dmidecode -s bios-version' or access BIOS setup to view the current BIOS firmware version

Affected if Unable to retrieve BIOS version - cannot determine status
Check System Firmware version

Run command 'dmidecode -s firmware-version' or use Intel System Firmware Update utility if available to view System Firmware version

Affected if Unable to retrieve System Firmware version - cannot determine status
Compare versions to fixed release

Compare the installed BIOS and System Firmware version numbers against the fixed version R01.02.0002. Earlier versions (e.g., R01.01.xxxx, R01.00.xxxx) are considered vulnerable

Affected if Installed version is numerically lower than R01.02.0002 - system is affected by this vulnerability

A user is affected if they own an Intel Server M50FCP system with BIOS or System Firmware version earlier than R01.02.0002, as the uncontrolled search path flaw exists in the firmware update process of those versions.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Intel firmware update R01.02.0002 or later to the affected Intel Server M50FCP family systems. This is a vendor-supplied patch that addresses the uncontrolled search path vulnerability.

Recommended fix Moderate confidence

R01.02.0002

Download the BIOS/System Firmware Update Package version R01.02.0002 for Intel(R) Server M50FCP family from Intel's official support website
Verify the integrity of the downloaded update package using checksums if provided
Apply the firmware update following Intel's standard BIOS/firmware update procedures for the Server M50FCP family
Reboot the system as required by the firmware update process to complete the installation
Confirm the installed firmware version is R01.02.0002 or later after the update

Caveat Firmware updates carry inherent risks and should be tested in a non-production environment before deployment; ensure backup of current configuration and have a recovery plan

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

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation4.0 h
Testing2.0 h
Review / QA2.0 h

12.0 hours of engineering $2,180

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

intel.com
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-42492 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-42492?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 6.7 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

Need this fixed?

Have this fixed 12 hrs · Moderate

Typical engagement from $2,180

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-42492 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References