CISA releases ESXiArgs ransomware recovery script
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2020-3992 | Use-After-Free RCE in VMware ESXi OpenSLP Service (Port 427) CVE-2020-3992 is a use-after-free (CWE-416) in the OpenSLP service used by VMware ESXi, rated critical at CVSS 9.8. An unauthenticated attacker with access to port 427 on an ESXi host's management network can send crafted SLP traffic that triggers the memory-reuse flaw and gains remote code execution on the hypervisor. Successful exploitation grants full control of the ESXi host, and attackers have used these OpenSLP flaws in the ESXiArgs ransomware campaign to encrypt the disks of hosted virtual machines. Affected products are ESXi 7.0, 6.7 and 6.5 prior to the October 2020 patch releases (as well as the related VMware Cloud Foundation). The flaw is in CISA's KEV catalog (added 2021-11-03) with ransomware use confirmed, and EPSS assigns an 83% probability of exploitation within 30 days (100th percentile); no public PoC is listed in the source data. Do: Apply VMware's ESXi security patches: ESXi_7.0.1-0.0.16850804 (7.0), ESXi670-202010401-SG (6.7), or ESXi650-202010401-SG (6.5), or the corresponding VMware Cloud Foundation update, per CISA's required action. As interim mitigation, restrict or disable the SLP service and firewall port 427 so ESXi management interfaces are not reachable from the internet. Because ransomware use is confirmed, check hosts for signs of compromise; CISA has published an ESXiArgs recovery script for affected deployments. | 9.8 | 83% | KEV ransomware |
| large≈90,000-100,000 internet-exposed ESXi hosts on port 427 (many more reachable only on internal management networks) | |
| CVE-2021-21974 | OpenSLP as used in ESXi (7.0 before ESXi70U1c-17325551, 6.7 before ESXi670-202102401-SG, 6.5 before ESXi650-202102101-SG) has a heap-overflow vulnerability. OpenSLP as used in ESXi (7.0 before ESXi70U1c-17325551, 6.7 before ESXi670-202102401-SG, 6.5 before ESXi650-202102101-SG) has a heap-overflow vulnerability. A malicious actor residing within the same network segment as ESXi who has access to port 427 may be able to trigger the heap-overflow issue in OpenSLP service resulting in remote code execution. NVD description · AI analysis pending | 8.8 | 45% | PoC |
| — |
Full article651 words · extracted from helpnetsecurity.com · click to collapse
According to the latest data, the number of ESXiArgs ransomware victims has surpassed 3,800, and CISA has published a recovery script for victim organizations.

Fixing the mess
The attacks started late last week and are still ongoing.
Investigations point to a new family of ransomware dubbed ESXiArgs by the researchers – though, according to Paul Ducklin, Sophos Head of Technology for the Asia Pacific region, it should be just Args, as it’s a Linux program that can be used against more than just VMWare ESXi systems and files.
The malware attempts to kill off running virtual machines, export an ESXi filesystem volume list, find important VMWare files for each volume, and call a general-purpose file scrambling tool for each file found, Ducklin explained.
But according to different sources, the first step of the process occasionally fails, and the encryption process is limited to a small chunk of data within files.
“Depending of your VM OS and file system type, you might be able to recover data with data revery tools, at least partially. Be carefull, this tools might have irreversible action on the file so, we recommend to copy the VM files on an other location to protect the data before trying any recovery operation,” warned Julien Levrard, CISO at OVHcloud.
To help organizations recover virtual machines affected by the ESXiArgs ransomware attacks, CISA has released a recovery script based on publicly available resources, including a tutorial by Enes Sonmez and Ahmet Aykac of the YoreGroup Tech Team.
“The tool works by reconstructing virtual machine metadata from virtual disks that were not encrypted by the malware. This script does not seek to delete the encrypted config files, but instead seeks to create new config files that enable access to the VMs,” CISA explained, but warned that organizations using it review it before deploying it, to determine if it is appropriate for their environment.
Preventing similar attacks
According to a recent list compiled by CISA technical advisor Jack Cable by combining the results of Censys’s scanning of internet-facing systems and a collection of Bitcoin addresses compiled by crowdsourced ransomware payment tracker Somewhere, over 3,800 systems have been hit by the ransomware.
VMware says they have “not found evidence that suggests an unknown vulnerability (0-day) is being used to propagate the ransomware used in these recent attacks.”
The French CERT says that the attackers are exploiting CVE-2021-21974, but possibly also an older vulnerability (CVE-2020-3992), to gain access to target systems. Both flaws affect ESXi’s SLP service, and VMware released patches for them years ago.
“The systems currently targeted would be ESXi hypervisors in version 6.x and prior to 6.7,” the CERT said. VMware advises users for upgrade to a supported version (ESXi 7.x or ESXi 8.x), implement any security patches provided and/or disabling the SLP service (and other unnecessary services). The company also noted that “in 2021, ESXi 7.0 U2c and ESXi 8.0 GA began shipping with the service disabled by default.”
UPDATE (February 9, 2023, 04:30 a.m. ET):
As a companion to the ESXiArgs recovery script released on Wednesday, CISA and the FBI have published a joint cybersecurity advisory offering guidance on to use the script and recover systems.
But, they warned, the script only serves as a method to recover essential services.
“Although CISA and FBI have not seen any evidence that the actors have established persistence, we recommend organizations take the following additional incident response actions after applying the script: review network logging to and from ESXi hosts and the guest VMs for unusual scanning activity, and review traffic from network segments occupied by the ESXi hosts and guests,” they advised.
“Organizations should also collect and review artifacts, such as running processes/services, unusual authentications, and recent network connections.”
Unfortunately, there’s also some unwelcome news: The attackers have started using a new ESXiArgs version that encrypts a bigger portion of the targeted files, making the recovery script obsolete.
Text extracted automatically; images, tables and formatting may be missing. Original: https://www.helpnetsecurity.com/2023/02/08/esxiargs-ransomware-recovery/