Urgent.News

What's breaking now, across thousands of outlets.

Tech

The VMware vCenter Zero-Day: A Management-Plane Breach and the Cost of Waiting

When the management plane is owned, the estate is suspect Most vulnerability stories describe a bug that was quietly patched and then forgotten. This one is different: a critical, unpatched flaw inside VMware vCenter was actively exploited in a zero-day campaign by a sophisticated Chinese Advanced Persistent Threat (APT) group, and the campaign was already underway before the vendor had a fix.…

The management plane of VMware vCenter has been compromised in a zero-day attack by a sophisticated Chinese Advanced Persistent Threat (APT) group. This critical flaw was actively exploited, even before VMware released a patch. The management plane is the central control for virtualised infrastructure systems, including databases, domain controllers, application servers, and backup systems. If compromised, every managed system becomes vulnerable.

The flaw allows for remote code execution (RCE) without the need for valid credentials. The attacker can execute arbitrary commands as though they originated from a trusted source, often with elevated privileges like root or SYSTEM. This means the attack bypasses standard authentication, runs with the privileges of the host or service account, and can scale to lead to full domain control over the virtual environment.

This zero-day incident highlights a significant gap in how organisations approach vulnerability management compared to the actual severity of a zero-day exploit. Traditional patch management cycles, such as quarterly or monthly schedules, are often insufficient when a vendor has not yet released a fix and the vulnerability is already being exploited.

Immediate, out-of-band patching cycles are required, along with explicit emergency paths for senior administrators to take isolated, narrowed mitigations until the vendor can provide a patch.

To mitigate the risk of such an attack, administrators and enterprises should apply the vendor patch immediately if available, isolate affected hosts, rotate credentials used by the management service, and reduce the attack surface on the management network. Restricting the management plane to known administrative sources and implementing micro-segmentation can prevent a foothold from escalating to domain control.

Auditing recent changes, service accounts, scheduled tasks, and network connections originating from the vCenter host, as well as reviewing credential hygiene, are also crucial steps to detect and respond to potential compromises.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Extending the UHPCM Patch Monitor Parser to Handle “Computer Name” Headers, Header‑less Pages, and Reboots Without an OC Column

Extending the UHPCM Patch Monitor Parser to Handle “Computer Name” Headers, Header‑less Pages, and Reboots Without an OC Column TL;DR: I refactored lib/parser.mjs to accept a single‑line “Computer…

  • UHPCM patch monitor parser extended to handle "Computer Name" headers.
  • Parser now accommodates pages without headers and reboots without OC column.
  • Changes ensure robust parsing across varied input formats.

More from Thursday 19 November →