CVE-2024-23487
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 · uneditedImproper input validation in UserAuthenticationSmm driver in UEFI firmware for some Intel(R) Server D50DNP Family products may allow a privileged user to 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 confidenceImproper input validation in the UserAuthenticationSMM driver in UEFI firmware for Intel Server D50DNP family products allows a privileged local user to escalate privileges. The vulnerability exists in System Management Mode (SMM), a highly privileged CPU mode, enabling potential complete system compromise.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify system modelCheck if the server is an Intel Server D50DNP family product (e.g., D50DNP, D50DNP2, D50DNP2L, or D50DNP2Q) by inspecting the system chassis label, BIOS setup screen, or using IPMI or other system inventory tools.Affected if The system is not an Intel D50DNP family product, then this specific CVE does not apply.
-
Check UEFI firmware versionAccess the BIOS/UEFI setup utility during boot (typically via F2 or DEL key) and locate the BIOS version information, or query via IPMI: 'ipmitool -I lanplus -H <ip> -U <user> -P <pass> raw' or similar command to retrieve firmware version. Compare your installed version against the Intel-provided firmware revision for the D50DNP family that addresses CVE-2024-23487.Affected if The installed firmware version has not been patched to include the fix for improper input validation in the UserAuthenticationSMM driver.
-
Verify SMM is enabledIn the UEFI/BIOS setup utility, navigate to the Security or Advanced settings and check the System Management Mode (SMM) configuration status. SMM is typically enabled by default on server platforms.Affected if System Management Mode is enabled in the firmware settings; this is the default and required condition for the vulnerability to be exploitable.
-
Confirm UserAuthenticationSMM driver presenceInspect the UEFI firmware image or the SMM driver list using tools such as UEFI tool (uefi_extract), Chipsec, or the system's firmware dump. Look for a driver named UserAuthenticationSMM or similar within the SMM drivers section.Affected if The UserAuthenticationSMM driver is present in the firmware and operates with the vulnerable input validation logic.
If the system is an Intel D50DNP family server with an unpatched UEFI firmware version and SMM is enabled, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the Intel firmware update for the D50DNP family products. Since this is a firmware-level vulnerability in SMM, no workarounds are available; the only remediation is patching the UEFI/BIOS.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23487 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23487 in production — separate from our analysis above.
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.
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.
- 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