Skip to main content
Menu
Breaches

Breach

Kaspersky reports BO Team exploited Log4Shell in VMware vCenter during intrusion at a Russian developer

Kaspersky's ICS CERT documented a months-long compromise of an unnamed Russian software developer's network, including theft of confidential information and a code-signing server.

SZB-1abe8912cb

Written by a model from the sources below. Verify against them.

Sources1Confirmed
Vendor
VMware
Product
vCenter Server
Status
Confirmed
Disclosed
Exploited vulnerability
BO Team

Summary

Kaspersky says the attackers gained root access to a vCenter 7.0.3 server through the Log4Shell flaw (CVE-2021-44228) and planted a backdoor on the hypervisor.

What to do

  • Upgrade vCenter Server or apply the vendor's Log4j fixes so the Log4Shell flaw (CVE-2021-44228) is no longer present.

  • Search hypervisors for the hourly cron script named "pgcache" in /etc/cron.hourly/ and remove any unauthorized backdoor.

  • Rotate credentials for vCenter, hypervisor SSH access and any accounts that touched the affected systems.

  • Verify the integrity of code-signing servers and CI/CD infrastructure before signing new releases.

Timeline

  1. Made public by The Hacker News
  2. First seen by cve.now
  3. Confirmed as CVE-2021-44228

Public exploit activity: CVE-2021-44228

5090100%0Aug 20Nov 17
  • GitHub PoC repos: 509
  • EPSS: 100.0%

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Exploited CVEs

CVE-2021-44228Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpointsCVSS 10.0In CISA KEVFixed in 2.3.1, 2.12.2

Evidence 1

  1. Press
    The Hacker News
    “However, the threat actor managed to successfully target a VMware vCenter server (version 7.0.3) vulnerable to CVE-2021-44228 (aka Log4Shell and LogJam), obtain a remote command line with root privileges, connect to the hypervisor over SSH, and identify accessible hosts.”

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about the VMware breach

Was VMware breached?

Yes. Confirmed as CVE-2021-44228.

What should VMware customers do?

Upgrade vCenter Server or apply the vendor's Log4j fixes so the Log4Shell flaw (CVE-2021-44228) is no longer present. Search hypervisors for the hourly cron script named "pgcache" in /etc/cron.hourly/ and remove any unauthorized backdoor. Rotate credentials for vCenter, hypervisor SSH access and any accounts that touched the affected systems. Verify the integrity of code-signing servers and CI/CD infrastructure before signing new releases.