Dell iDRAC10 (credential handling, race condition): A race in iDRAC10's credential handling leaves secrets

Impact

A race in iDRAC10's credential handling leaves secrets insufficiently protected, letting an authenticated low-privilege user win the race and come back with elevated access to the BMC. Elevated on the BMC means the whole out-of-band toolkit: power, Virtual Media, KVM, firmware. This one matters disproportionately because iDRAC10 ships on 17G PowerEdge - the newest GPU platforms - so the affected fleet is the freshly-racked capacity, not the legacy tier, and it is likely still inside its burn-in window where firmware is whatever shipped from the factory.

Who can reach it

An authenticated low-privilege iDRAC10 account. The exposure is anyone you have handed a non-admin BMC login: remote hands, an integrator, a monitoring service account, or a tenant-facing self-service console that proxies BMC actions.

What to do

Flash iDRAC10 to 1.30.10.50 or later. Affected builds are 1.20.70.50 and 1.30.05.10 specifically. Out-of-band, per-node, no host reboot and no job drain. Because this hits new deployments, fold the check into rack-acceptance: verify iDRAC10 build before a node ever takes tenant traffic, rather than discovering it in a later sweep. No config-only mitigation - reduce exposure meanwhile by pruning low-privilege iDRAC accounts.

References