Database/Firmware, BMC & network fabric

ArubaOS GRUB2 implementation (secure boot): Two flaws in ArubaOS's GRUB2 implementation allow secure boot
Impact
Two flaws in ArubaOS's GRUB2 implementation allow secure boot to be bypassed, leading to remote compromise. Secure boot on a network device is the control that stops a compromise from becoming permanent; bypassing it means an attacker's image survives reimaging and firmware updates. Same structural problem as the Cisco NX-OS image-verification bypass, on a different vendor.
Who can reach it
An attacker able to influence the boot chain — via administrative access or the documented remote path.
What to do
ArubaOS upgrade plus reload; this is a bootloader-level fix so it must be applied per device and cannot be worked around in config. Treat any device suspected of pre-patch compromise as needing replacement or a verified out-of-band reflash rather than an in-place upgrade.
References
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.