dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-22095

HIGH · 7.2 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 →
72/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
Improper input validation in PlatformVariableInitDxe 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 · moderate confidence

Improper input validation vulnerability in the PlatformVariableInitDxe driver of UEFI firmware on Intel Server D50DNP Family products allows a privileged local user to escalate privileges by exploiting insufficient validation of input data handled during the firmware initialization phase.

MitigationApply the Intel firmware update for D50DNP family products once released, after verifying compatibility in a test environment.

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:H/UI:R/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 checks

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

  1. Identify the server model
    Run 'dmidecode -s system-product-name' or check the physical server label to confirm it is an Intel Server D50DNP Family system
    Affected if The system is an Intel D50DNP-series server
  2. Retrieve the UEFI firmware version
    Run 'dmidecode -s bios-version' from the operating system, or enter UEFI setup and navigate to the BIOS/Platform Information screen to view the firmware version
    Affected if The firmware version is older than Intel's fixed version for this CVE
  3. Check if PlatformVariableInitDxe driver is loaded
    From Linux, inspect UEFI variable boot logs or use 'efivars' to enumerate loaded UEFI drivers during boot; alternatively, examine the UEFI firmware image for the PlatformVariableInitDxe driver presence using UEFI firmware extraction tools
    Affected if The PlatformVariableInitDxe driver is present in the UEFI firmware
  4. Verify local privileged access context
    Confirm the existence of local administrator or root accounts on the system, as the vulnerability requires a privileged local user to exploit
    Affected if Local privileged accounts exist and the firmware is unpatched

The system is affected if it is an Intel Server D50DNP running UEFI firmware with the PlatformVariableInitDxe driver at a version prior to Intel's fixed release for CVE-2024-22095.

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 the Intel firmware update for D50DNP family products once released, after verifying compatibility in a test environment.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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