dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2024-23980

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 buffer restrictions in PlatformPfrDxe driver in UEFI firmware for some Intel(R) Server D50FCP 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 confidence

A buffer restriction vulnerability exists in the PlatformPfrDxe driver within UEFI firmware on Intel Server D50FCP Family products. The improper buffer restrictions allow a privileged local user to escalate their privileges, likely through memory corruption or buffer overflow exploitation in the Platform Firmware Resilience (PFR) driver.

MitigationApply the latest UEFI firmware update provided by Intel for the affected Server D50FCP Family products. Until the firmware patch is available, limit physical and local access to trusted only, as the vulnerability requires a privileged user with local access.

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 command 'dmidecode -s system-product-name' or check BIOS/UEFI setup for the product name to confirm it is an Intel Server D50FCP Family system
    Affected if The system is NOT an Intel Server D50FCP Family product (not affected)
  2. Check if Platform Firmware Resilience (PFR) is enabled
    Access UEFI BIOS setup and locate the PFR configuration under 'Platform Firmware Resilience' or 'PFR' settings menu. Verify whether PFR is currently enabled or disabled
    Affected if PFR is enabled in the UEFI settings (the vulnerability applies to the PFR driver)
  3. Verify UEFI firmware version
    Run command 'dmidecode -s bios-version' or check the UEFI BIOS setup information screen to obtain the current firmware version installed on the system
    Affected if The installed firmware version is older than the latest Intel-provided patch for D50FCP Family (compare against Intel's firmware release notes)
  4. Check PlatformPfrDxe driver version
    Access UEFI shell or use 'dmiutil' to enumerate PFR-related UEFI drivers. The PlatformPfrDxe driver version can often be found in the UEFI driver menu under 'Driver Health' or by dumping UEFI variables related to PFR
    Affected if The PlatformPfrDxe driver version matches the vulnerable version range (contact Intel support for specific vulnerable versions)
  5. Confirm local privileged access exists
    Review system audit logs and user account configurations to determine if any non-administrator accounts with local access exist on the system
    Affected if Local privileged user accounts exist on the system (prerequisite for exploitation)
  6. Inspect system for exploitation indicators
    Review system memory dumps or firmware integrity logs for unexpected memory writes in the PFR driver memory region. Check UEFI variable 'PfrLog' if available via 'efivar -n' command
    Affected if Anomalous memory patterns or unauthorized firmware modifications detected in PFR-related memory areas

A user is affected if they are running an Intel Server D50FCP Family system with PFR enabled and a firmware version prior to Intel's patched release, and they have local privileged access that could be exploited.

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 latest UEFI firmware update provided by Intel for the affected Server D50FCP Family products. Until the firmware patch is available, limit physical and local access to trusted only, as the vulnerability requires a privileged user with local access.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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