# CVE-2024-10237: SMC BMC Firmware Image Authentication Design Issue

> Attackers can modify BMC firmware to bypass signature verification, enabling unauthorized code execution and privilege escalation on Supermicro servers.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2025
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-hj75-v4c2-73ch

## What is CVE-2024-10237?

CVE-2024-10237 is a high-severity vulnerability in SMCI MBD-X12DPG-OA6, published on 4 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

There is a vulnerability in the BMC firmware image authentication design 

 at Supermicro MBD-X12DPG-OA6

. An attacker can modify the firmware to bypass BMC inspection and bypass the signature verification process

Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2024-10237?


## How do I fix CVE-2024-10237?

No fix has been published for CVE-2024-10237 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-10237 being exploited?

There is no known exploitation of CVE-2024-10237 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10237 and fix it if it is affected.

What it is: CVE-2024-10237 is a high-severity vulnerability in SMCI MBD-X12DPG-OA6, published on 4 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10237 in the wild and no public exploit code.

Affected product: SMCI MBD-X12DPG-OA6. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-10237/ (Markdown: https://insights.sbomify.com/CVE-2024-10237/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10237
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10237
- OSV: https://osv.dev/vulnerability/CVE-2024-10237

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-10237/
Summaries are generated and may contain mistakes; the official description above is the record.