dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-28047

MEDIUM · 5.3 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 →
55/100
Remediation priority · Elevated
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 UEFI firmware for some Intel(R) Processors may allow a privileged user to potentially enable information disclosure 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

This is a firmware vulnerability in UEFI (Unified Extensible Firmware Interface) for certain Intel processors. The issue stems from improper input validation (CWE-20) that could allow a privileged user with local access to the system to potentially obtain sensitive information through the firmware interface.

MitigationApply the appropriate UEFI/BIOS firmware update provided by Intel for affected processors. Organizations should inventory affected hardware and schedule firmware updates following vendor guidance, ensuring proper backup and recovery procedures are in place.

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
None
Availability
None

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N

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 your processor vendor and model
    Run system information commands (such as 'dmidecode -t processor' on Linux or check System Information in Windows) to confirm if the system uses an Intel processor. For servers, check the BMC/IPMI for processor details.
    Affected if The system does not use an Intel processor in the affected product line (no Intel processors are vulnerable to this specific UEFI flaw).
  2. Determine the installed UEFI/BIOS firmware version
    Access the UEFI/BIOS setup interface during boot (typically via F2, F12, or Delete key) and record the BIOS/UEFI version string. On Linux, you can also use 'dmidecode -t bios' to retrieve the firmware version. On Windows, run 'wmic bios get smbiosbiosversion' or check in System Information.
    Affected if The installed UEFI/BIOS version is older than the version that addresses CVE-2024-28047 (you must compare against Intel's published advisory for this CVE to determine the patched version).
  3. Check for Intel processor family vulnerability status
    Consult Intel's official security advisory (INTEL-SA-00946 or related) for CVE-2024-28047 to identify which specific processor generations or families are affected. Cross-reference your processor model number from step 1 against the affected product list in the advisory.
    Affected if Your Intel processor model falls within the affected processor families listed in Intel's advisory for this CVE.
  4. Assess local privileged access exposure
    Review system access controls and audit logs to determine if any untrusted local users have privileged (administrator/root) access to the system. Check group membership and sudo/Administrator permissions.
    Affected if Untrusted or unpatched local privileged accounts exist on the system with administrator or root privileges, which satisfies the local privileged attacker requirement for exploitation.

You are affected if your system uses an Intel processor within the affected families AND runs a UEFI/BIOS version older than the patched version published in Intel's security advisory for CVE-2024-28047, and untrusted local privileged users have access to the system.

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 appropriate UEFI/BIOS firmware update provided by Intel for affected processors. Organizations should inventory affected hardware and schedule firmware updates following vendor guidance, ensuring proper backup and recovery procedures are in place.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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