VMware Fixes Vulnerabilities Exploited at Pwn2Own Berlin

VMware Fixes Vulnerabilities Exploited at Pwn2Own Berlin


Following successful live exploit demonstrations at the Pwn2Own Berlin 2025 security competition held in May, VMware has patched four zero-day vulnerabilities affecting several of its virtualization products, including ESXi, Workstation, Fusion, and VMware Tools. These vulnerabilities pose critical security risks, especially for enterprise environments using ESXi to run virtualized infrastructure.

Background: What Is Pwn2Own?

Pwn2Own is a renowned global hacking competition where top cybersecurity researchers showcase their expertise by exploiting real-world systems and software. It is organized by Trend Micro’s Zero Day Initiative (ZDI) and rewards researchers with substantial cash prizes for valid zero-day exploits.

During Pwn2Own Berlin 2025, several researchers targeted VMware products with alarming success. Their efforts revealed multiple critical flaws that VMware engineers have now addressed with urgent updates.

The Vulnerabilities

1. CVE-2025-41236 – Heap Buffer Overflow via VMXNET3

  • Severity: Critical (CVSS 9.3)
  • Component Affected: VMXNET3 virtual network adapter
  • Impact: Allows a guest virtual machine (VM) to escape to the host—i.e., attackers can execute arbitrary code on the host system running the VM.
  • Technical Summary: This flaw is an integer overflow vulnerability in the VMXNET3 device. When memory allocations are computed using unchecked arithmetic, attackers can overflow values, leading to a buffer that is too small to hold incoming data. An overflow from this condition ultimately enables arbitrary memory writes on the host.
  • Key Exploit: Demonstrated by STARLabs SG, winning $150,000 in rewards.

2. CVE-2025-41237 – Integer Underflow via VMCI

  • Severity: Critical (CVSS 9.3)
  • Component Affected: Virtual Machine Communication Interface (VMCI)
  • Impact: Allows code execution on the host system from a guest VM.
  • Technical Summary: VMCI facilitates communication between VMs and the host, including data and signal passing. The reported bug involves an integer underflow, a scenario in which numeric operations wrap around to very large values (e.g., subtracting 1 from 0 gives 4 billion in unsigned 32-bit integers). This leads to out-of-bounds memory writes, which can corrupt host memory and allow malicious code execution.

3. CVE-2025-41238 – Out-of-Bounds Heap Write via PVSCSI

  • Severity: Critical (CVSS 9.3)
  • Component Affected: Paravirtual SCSI Controller (PVSCSI)
  • Impact: Guest-to-host code execution via heap memory corruption.
  • Technical Summary: This flaw lies in how the paravirtual SCSI (storage) controller handles crafted inputs. Improper bounds checking on memory buffers passed from guest VMs results in heap-based out-of-bounds writes. These write operations can overwrite critical data structures, leading to arbitrary code execution on the host.

4. CVE-2025-41239 – Information Disclosure via vSockets

  • Severity: High (CVSS 7.1)
  • Component Affected: Virtualized Sockets (vSockets)
  • Impact: Leaks sensitive host memory to the attacking VM.
  • Technical Summary: vSockets are used for communication between VMs and between a VM and the host. This flaw permits attackers with administrative privileges inside the guest to read uninitialized memory, potentially exposing sensitive host data, cryptographic material, or memory layout info useful in chaining exploits.

Affected VMware Products and Versions

  • ESXi: 8.0/7.0 (various sub-versions; refer to VMware’s Security Advisory for full details)
  • Workstation Pro: 17.x
  • Fusion: 13.x
  • VMware Tools: Update to 13.0.1.0

📝 Note: Please refer to the full VMware Security Advisory VMSA-2025-0013 for specific build numbers and platform fixes.

Who Discovered These Vulnerabilities?

All four flaws were responsibly disclosed to VMware through the Zero Day Initiative following live demonstrations at Pwn2Own Berlin 2025: Research Team Vulnerabilities Exploited Awards Received STARLabs SG CVE-2025-41236 $150,000 Synacktiv CVE-2025-41237, CVE-2025-41238 $140,000+ Reverse Tactics CVE-2025-41239 $50,000

Potential Threat and Urgency

  • While there is no public evidence of these flaws being used in the wild, the fact that they enable guest-to-host escapes makes them extremely dangerous.
  • In a cloud or data center environment where ESXi hosts run multiple virtual machines from different tenants, a successful exploit could result in cross-tenant breaches.
  • These types of exploits are invaluable to advanced persistent threat (APT) groups or nation-state actors, particularly in scenarios targeting cloud or multi-tenant environments.

Recommended Actions

1. Apply Patches Immediately

If your organization is running affected versions of ESXi, Workstation, Fusion, or VMware Tools, apply the relevant security updates without delay. Refer to the official advisory and download patches through VMware’s Customer Connect portal or via your configuration management workflows.

2. Update VMware Tools in Guest VMs

Even if the hypervisor itself is patched, vulnerability CVE-2025-41239 affects guest-facing components. Be sure to roll out updated VMware Tools (13.0.1.0 or later) to all VMs.

3. Audit Virtual Machine Access

Limit administrative privileges on guest VMs. Exploits rely on local admin/root access inside the VM to execute commands that trigger host-level vulnerabilities.

4. Consider Enabling Additional Isolation

On sensitive infrastructure, consider increased VM isolation using features like VMware vSphere VM Encryption, vTPM, or I/O Filtering to reduce exposure to device-related attack surfaces.

Final Thoughts

VMware’s fast response to these zero-day vulnerabilities highlights the importance of proactive security measures and collaboration with the global research community. These flaws demonstrate that hypervisors—foundational to cloud workloads and enterprise virtualization—remain high-value targets.

While no active exploitation has been detected in the wild, organizations cannot afford to wait on patching. Immediate risk mitigation is critical, especially in environments hosting sensitive workloads or providing services to multiple tenants.

Comments

No comments yet. Why don’t you start the discussion?

    Leave a Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.