Safeguard
Vulnerability Analysis•

CVE-2023-3043: Critical Stack Overflow in AMI MegaRAC SP-X BMC

CVE-2023-3043 is a critical (9.6) stack buffer overflow in AMI MegaRAC SP-X BMC firmware reachable from an adjacent network. Apply the vendor firmware fix.

Safeguard Security Team
3 min read

CVE-2023-3043 is a critical (CVSS 9.6) stack based buffer overflow in AMI's SPx firmware for the MegaRAC baseboard management controller. An attacker on an adjacent network can trigger it. I could not confirm fixed versions, so apply the firmware update named in AMI advisory AMI-SA-2023010.

What's affected

The record lists AMI MegaRAC SP-X, with no version range. AMI's advisory, number AMI-SA-2023010, is the only reference, and it was not readable for me. Because server makers and hardware vendors ship AMI's code under their own firmware versions, the update you need is usually published by your server vendor.

The NVD record was published on 9 January 2024. The vector is adjacent network, low complexity, no privileges, no interaction, with changed scope. Adjacent means the attacker needs to be on the same network segment, such as the management network.

How to check if you're exposed

Find out which of your servers have a BMC based on AMI MegaRAC. Your server vendor's management interface, often named iLO, iDRAC or a generic web BMC, shows the firmware version under system information. Utilities such as ipmitool mc info can also report the BMC's firmware revision.

Then compare against your server vendor's security bulletin for AMI-SA-2023010.

What to do now

  1. Inventory servers with an AMI MegaRAC BMC and their firmware revisions.
  2. Apply the BMC firmware update from your server vendor that addresses this advisory.
  3. Keep BMC interfaces on an isolated management network, and never expose them to the internet.
  4. Limit which hosts can sit on the same segment as the BMCs.
  5. Review BMC accounts and rotate credentials after updating.

Why it matters

The record maps this to CWE-121, a stack based buffer overflow, and CWE-787, out-of-bounds write. Firmware code copies data into a fixed size stack buffer without checking the length, and the extra data overwrites neighboring memory.

A BMC sits below the operating system and often has power control, console access and a path to the server's firmware. Loss of confidentiality, integrity and availability are all rated high, and the changed scope reflects that the BMC can affect the host. KEV is false. Network isolation limits exposure while firmware updates roll out, which can be slow for hardware.

Quick check

What does adjacent network mean?

The attacker must be on the same local network segment as the BMC, not anywhere on the internet.

Where do I get the fix?

AMI's advisory AMI-SA-2023010 and your server vendor's firmware bulletins.

Sources

You can also run the free in-browser dependency scan at gold.safeguard.sh/scan to see which known vulnerabilities your dependencies carry.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.