AMI AptioV UEFI BIOS (SMM): A memory-bounds bug in the BIOS that lets an attacker execute code outside the intended

Impact

A memory-bounds bug in the BIOS that lets an attacker execute code outside the intended System Management Mode. What sets it apart from the rest of the AptioV set is the attack vector: AMI scores it as network-reachable, not local. A firmware bug you can reach over the wire is a different risk class from one that needs host root first - it means the BIOS attack surface is exposed through a management path rather than only through the host OS, and network segmentation of that path becomes load-bearing.

Who can reach it

Network, with high privileges required - an administrative account on whichever management path exposes the BIOS operation. In practice that means a BMC or out-of-band management credential, which is why this bug chains so naturally with the MegaRAC credential and REST API issues in this same cluster: BMC admin access becomes host firmware code execution.

What to do

BIOS update to BKC_5.37 or later - firmware flash plus a host reboot, per node, vendor-rebase-gated. Because the vector is network with privileges, there is real config-only mitigation available now: isolate the BMC and management plane so that no untrusted party can reach the privileged management interface, and give every node unique management credentials so one leak does not reach the fleet.

References