dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2024-38805

MEDIUM · 6.3 CVSS v3.1 Published 2025-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/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
EDK2 contains a vulnerability in BIOS where a user may cause an Integer Overflow or Wraparound by network means. A successful exploitation of this vulnerability may lead to denial of service.

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

EDK2 UEFI firmware contains an integer overflow vulnerability in its network-related BIOS components. The vulnerability can be triggered via network means (likely during PXE boot or network configuration), potentially causing a denial of service condition.

MitigationApply vendor-supplied BIOS/firmware updates from affected system manufacturers. Until patches are available, limit exposure of affected systems to untrusted networks.

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 if the system uses EDK2-based UEFI firmware
    Check the system BIOS/UEFI setup or system information for firmware vendor details. Common systems using EDK2 include Intel-based platforms, certain ARM servers, and various OEM systems that source UEFI from EDK2 upstream. Look for 'EDK2', 'TianoCore', or the firmware vendor's specific EDK2-based firmware name in the BIOS setup or via tools like 'dmidecode' on Linux (dmidecode -s bios-version) or 'msinfo32' on Windows.
    Affected if The system firmware is identified as an EDK2 or TianoCore-based UEFI implementation
  2. Determine the installed UEFI firmware version
    Retrieve the firmware version from the system. On Linux, use 'dmidecode -s bios-version' or check /sys/class/dmi/id/. On Windows, run 'msinfo32' or 'wmic bios get smbiosbiosversion'. On some systems, the version may be visible in the UEFI setup under 'Main' or 'Information' and may include a build date.
    Affected if The firmware version cannot be verified as patched, or the version is older than any vendor-supplied patch for CVE-2024-38805 (specific version ranges vary by OEM)
  3. Check if PXE boot or network boot is enabled
    Enter the UEFI/BIOS setup (typically press Del, F2, or F12 during boot) and navigate to the Boot menu. Look for 'PXE Boot', 'Network Boot', 'Ethernet Boot', 'iSCSI Boot', or similar network boot options. Check if these are set to Enabled, or inspect via boot configuration tools if available.
    Affected if PXE boot, network boot, or other network stack features are enabled in the UEFI configuration
  4. Verify the presence of network-related UEFI drivers
    From the UEFI shell or using a tool that can dump UEFI variables (like 'efivar' on Linux), check for loaded network drivers or explore the UEFI device menu. Look for drivers such as 'MnpDxe', 'ArpDxe', 'UdpDxe', 'TcpDxe', or other network stack components that are part of the EDK2 Network package.
    Affected if Network stack drivers/modules are loaded or available in the UEFI environment, particularly those supporting PXE or HTTP boot

A system is likely affected if it runs an EDK2-based UEFI firmware with network/PXE boot capabilities enabled, and the firmware version is not confirmed as patched by the system manufacturer.

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 vendor-supplied BIOS/firmware updates from affected system manufacturers. Until patches are available, limit exposure of affected systems to untrusted networks.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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