dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2024-10239

HIGH · 7.2 CVSS v3.1 Published 2025-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
A security issue in the firmware image verification implementation at Supermicro MBD-X12DPG-OA6 . An attacker with administrator privileges can upload a specially crafted image, which can cause a stack overflow due to the unchecked fat->fsd.max_fld.

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

Stack buffer overflow vulnerability in Supermicro X12DPG-OA6 motherboard firmware image verification. An authenticated administrator can upload a specially crafted firmware image containing an oversized fat->fsd.max_fld value that overflows a stack buffer during verification, potentially allowing code execution or denial of service.

MitigationRestrict administrative access to the IPMI/BMC interface. Apply the vendor-supplied firmware patch when available. Verify all firmware images before upload using cryptographic signatures.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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 motherboard model
    Access IPMI/BMC web interface or use IPMI command (ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> raw commands) to query BMC for product info. Alternatively, physically inspect the motherboard or check system documentation for model number.
    Affected if The motherboard is NOT the Supermicro X12DPG-OA6 model (vulnerability only affects this specific model).
  2. Determine the installed firmware version
    Access IPMI/BMC web interface and navigate to firmware version information, or use IPMI command: ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> fru print. Record the firmware version string.
    Affected if Unable to compare installed firmware version to vendor patch version (when released) - the system is running an unpatched version if the vendor has released a fix.
  3. Verify IPMI/BMC network accessibility
    Check if the BMC interface has an active IP address and is reachable on the network. Use ping or port scan (TCP 443 for HTTPS, TCP 80 for HTTP) from an external system.
    Affected if The BMC is network-accessible from untrusted networks - the attack requires network access to the IPMI interface.
  4. Confirm administrative account existence
    Check IPMI/BMC user list via web interface or command: ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> user list. Verify if administrator-level accounts exist and are enabled.
    Affected if No administrative accounts are configured or enabled - the vulnerability requires an authenticated administrator to upload a crafted firmware image.
  5. Check firmware upload feature status
    Access IPMI/BMC web interface and look for firmware update/upload functionality (usually under Maintenance, Firmware Update, or BIOS Update sections). Verify if this feature is available and not disabled.
    Affected if The firmware upload feature is accessible to the authenticated administrator - the vulnerability is triggered during firmware image verification.

The system is affected if it is a Supermicro X12DPG-OA6 motherboard with firmware upload enabled, accessible IPMI/BMC interface, and at least one authenticated administrator account - allowing a specially crafted firmware image to trigger the stack buffer overflow.

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

Restrict administrative access to the IPMI/BMC interface. Apply the vendor-supplied firmware patch when available. Verify all firmware images before upload using cryptographic signatures.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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