dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-22382

HIGH · 7.5 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 →
77/100
Remediation priority · High
Zero-click

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 PprRequestLog module 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 in the PprRequestLog module of UEFI firmware for Intel Server D50DNP Family products allows a local privileged user to escalate privileges through malformed input to the affected module.

MitigationApply the Intel firmware update for D50DNP family products when available, following Intel's recommended firmware update procedures.

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 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 branding for Intel Server D50DNP family designation
    Affected if The system is NOT an Intel Server D50DNP family product (the vulnerability only affects this specific product line)
  2. Determine the UEFI firmware version
    Run 'dmidecode -s bios-version' or access UEFI setup (F2 during boot) to view the BIOS/UEFI firmware version
    Affected if The installed UEFI firmware version falls within the affected version range for D50DNP family products (compare your version to Intel's advisory for this CVE)
  3. Verify PprRequestLog module presence
    Check UEFI firmware image or use UEFI shell tools to list loaded modules - look for 'PprRequestLog' or similar naming in the UEFI firmware components
    Affected if The PprRequestLog module is present in the UEFI firmware (the vulnerability exists in this specific module)
  4. Check for related PPE configuration
    Examine UEFI variable settings or hardware logs related to Processor Programming Interface (PPE) request logging - these may be visible in IPMI SEL logs or UEFI diagnostics
    Affected if PPE request logging features are enabled and the system processes requests through the PprRequestLog module (malformed input to this module enables privilege escalation)

The system is affected if it is an Intel Server D50DNP family product running UEFI firmware with the PprRequestLog module present and vulnerable version installed.

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 when available, following Intel's recommended firmware update procedures.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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