Database/Firmware, BMC & network fabric
HPE iLO4: Authentication bypass and remote code execution — the "29 A's" `Connection` header bug
Impact
Authentication bypass and remote code execution — the "29 A's" Connection header bug; trivially scriptable pre-auth root on the BMC
Who can reach it
Network, unauthenticated
What to do
iLO4 firmware update to 2.53+; a node left unpatched here is fully owned by a single curl request
Fleet impact
How widespread
common - iLO is HPE's BMC across ProLiant/Apollo, incl. GPU-dense SKUs
Cost to remediate
firmware-flash to iLO >= 2.54 on every node, out-of-band; the exploit is trivial (a long header) and public, so exposure windows are measured in hours
Why it hits the whole fleet
Unauthenticated remote auth bypass into the BMC yields administrator on the management processor, virtual-media boot of attacker media, and firmware-level persistence under the OS - identical across every HPE node of that generation.
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.