Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-22273 Overview
CVE-2024-22273 is an out-of-bounds read/write vulnerability affecting the storage controllers in VMware ESXi, Workstation, and Fusion. A malicious actor with access to a virtual machine that has storage controllers enabled can trigger the flaw to cause a denial of service condition. When chained with other issues, the vulnerability may enable code execution on the hypervisor from within a guest VM, representing a virtual machine escape scenario. The flaw is tracked under CWE-125 and is addressed in Broadcom Security Advisory #24308.
Critical Impact
Guest-to-hypervisor code execution risk when combined with other vulnerabilities, breaking the VM isolation boundary that underpins virtualized infrastructure.
Affected Products
- VMware ESXi 7.0 and 8.0 (multiple update branches)
- VMware Workstation and VMware Fusion (on Apple macOS)
- VMware Cloud Foundation
Discovery Timeline
- 2024-05-21 - CVE-2024-22273 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-22273
Vulnerability Analysis
The vulnerability resides in the storage controller emulation code of the VMware hypervisor. Guest operating systems interact with virtualized storage controllers through I/O operations that are serviced by the hypervisor process on the host. The affected code paths fail to properly validate buffer boundaries when processing certain storage controller requests. This leads to both out-of-bounds reads and out-of-bounds writes in host memory.
An attacker with local access to a guest VM, and the privileges needed to issue storage controller I/O, can craft malicious requests from inside the VM. The resulting memory corruption can crash the hypervisor process, producing a denial of service across hosted workloads. When combined with an information disclosure primitive or an additional memory corruption bug, the write primitive can be used to execute arbitrary code in the hypervisor context on the host.
Root Cause
The root cause is improper bounds checking on data buffers used by the emulated storage controllers. The flaw maps to CWE-125 Out-of-bounds Read and extends to out-of-bounds writes. The attack surface is reachable from any guest configured with the affected storage controller types.
Attack Vector
Exploitation requires local access to a guest VM with storage controllers enabled and low-privilege credentials inside that guest. No user interaction on the host is required. The attacker triggers the condition by issuing malformed storage I/O operations from the guest kernel or a privileged guest process. The vulnerability does not require network access to the host, but a networked attacker who compromises a guest can pivot to this local attack. See the Broadcom Security Advisory #24308 for vendor-provided technical scope.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2024-22273
Indicators of Compromise
- Unexpected vmx process crashes or hypervisor worker process terminations on ESXi, Workstation, or Fusion hosts.
- Guest VM power state transitions or vmware.log entries referencing storage controller faults, assertion failures, or backtraces.
- Host-side kernel logs or vmkernel.log entries indicating anomalous storage emulation errors tied to a specific guest.
Detection Strategies
- Monitor vmware.log files for repeated storage controller errors originating from the same guest VM.
- Correlate guest-side privilege escalation or kernel driver loads with subsequent hypervisor instability events.
- Baseline normal vmx process behavior and alert on crashes, respawns, or child process creation patterns inconsistent with that baseline.
Monitoring Recommendations
- Centralize ESXi host logs via syslog into a SIEM or data lake and build detections around storage controller error signatures.
- Track VM configuration changes that add or modify storage controllers on untrusted or multi-tenant workloads.
- Alert on hypervisor process crashes correlated with guest activity windows for rapid triage.
How to Mitigate CVE-2024-22273
Immediate Actions Required
- Apply the fixed versions of VMware ESXi, Workstation, Fusion, and Cloud Foundation as listed in Broadcom Security Advisory #24308.
- Inventory all hosts and identify guests with storage controllers that match the vulnerable configurations.
- Restrict administrative and local access to guest VMs on shared or multi-tenant hypervisors until patching is complete.
Patch Information
Broadcom has released fixed builds for VMware ESXi 7.0 and 8.0 update streams, VMware Workstation, VMware Fusion, and VMware Cloud Foundation. Consult Broadcom Security Advisory #24308 for the exact fixed build numbers that correspond to your deployed version.
Workarounds
- Where patching is delayed, remove unused storage controllers from guest VM configurations to reduce the attack surface.
- Limit who can log in to guest operating systems and enforce least-privilege for in-guest accounts and services.
- Isolate sensitive hosts from untrusted guest workloads until fixed builds are deployed.
# Verify ESXi build version against the fixed builds listed in advisory #24308
vmware -vl
esxcli system version get
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

