AMI MegaRAC SP-X and OpenBMC
CVE-2023-52916
In the Linux kernel, the following vulnerability has been resolved: media: aspeed: Fix memory overwrite if timing is 1600x900 When capturing 1600x900, system could crash when system memory usage is tight. The way to reproduce this issue: 1. Use 1600x900 to display on host 2. Mount ISO through 'Virtual media' on OpenBMC's web 3. Run script as below on host to do sha continuously #!/bin/bash while [ [1] ]; do find /media -type f -printf '"%h/%f"\n' | xargs sha256sum done 4. Open KVM on OpenBMC's web The size of macro block captured is 8x8. Therefore, we should make sure the heigh...
What to do
NVD gives no version range for this CVE yet, so this page cannot name an update version. Read the vendor advisory for the fixed firmware.
NVD names no vendor advisory for it. Look it up at AMI and OpenBMC security advisories (search for CVE-2023-52916).
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-52916. 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.