Dell OpenManage Enterprise (remote code execution): Remote code execution on the OpenManage Enterprise console

Impact

Remote code execution on the OpenManage Enterprise console. OME is the fleet-wide control plane that already holds credentials for, and can push firmware to, every iDRAC it manages - so compromising it is not compromising one node, it is compromising the mechanism that drives all of them. An attacker in OME can trigger firmware deployment, mount Virtual Media, and power-cycle at fleet scale from a single box. Affects OME versions before 3.6.2 and the corresponding OME-Modular builds.

Who can reach it

An attacker with access to the immediate subnet the OME appliance sits on. That is usually the management network segment, so the practical question is who else lives on the same VLAN as your OME appliance - jump hosts, monitoring, DCIM, and often a broader IT segment than anyone intends.

What to do

Upgrade the OME appliance to 3.6.2 or later. This is a single appliance upgrade, not a per-node campaign, so it is cheap in rollout terms - no node reboots, no job drain, only the OME console's own downtime. The structural fix is network placement: put OME on its own segment with an explicit allowlist rather than sharing the general management VLAN, and treat it as tier-0 infrastructure because it holds BMC credentials for the whole fleet.

References