AMI MegaRAC SP-X and OpenBMC
CVE-2023-37297
AMI’s SPx contains a vulnerability in the BMC where an Attacker may cause a heap memory corruption via an adjacent network. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.
Affected versions (NVD)
| Product | Versions |
|---|---|
| megarac_sp-x | >= 12, < 12.7 |
| megarac_sp-x | >= 13, < 13.6 |
What to do
NVD marks firmware before these versions as affected: megarac_sp-x before 12.7; megarac_sp-x before 13.6. The usual fix is to update to that version or later. Vendors patch each firmware branch separately, so confirm the fixed build for your branch in the advisory.
Vendor advisory (from the NVD record): 9443417.fs1.hubspotusercontent-na1.net/hubfs/9443417/Security%20Adviso · 9443417.fs1.hubspotusercontent-na1.net/hubfs/9443417/Security%20Adviso.
Do you run it?
Paste your BMC's Redfish answers into the Redfish Inspector: it compares the firmware version with the NVD ranges, in your browser. Or scan every BMC with the free scan.
Source: NVD CVE-2023-37297. PWX for MegaRAC and OpenBMC
Run it on your own fleet
PWX Discover is free: the scan reads your fleet and lists what to fix, on your machine. PWX Monitor keeps watching every layer, from the tenant to the power rail, with attack paths and alerts in your SIEM. PWX Protect acts on the BMC. Start with a pilot.