PVSCSI heap-overflow vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in ESXi80U3f-24784735, ESXi80U2e-24789317, ESXi70U3w-24784741, 17.6.4, 13.6.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
VMware ESXi, Workstation, and Fusion contain a heap-overflow vulnerability in the PVSCSI (Paravirtualized SCSI) controller that leads to an out of-bounds write. A malicious actor with local administrative privileges on a virtual machine may exploit this issue to execute code as the virtual machine's VMX process running on the host. On ESXi, the exploitation is contained within the VMX sandbox and exploitable only with configurations that are unsupported. On Workstation and Fusion, this may lead to code execution on the machine where Workstation or Fusion is installed.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- VMware ESXi
From 8.0 · fixed in ESXi80U3f-24784735; From 8.0 · fixed in ESXi80U2e-24789317; From 7.0 · fixed in ESXi70U3w-24784741
- VMware Cloud Foundation
Version range not reported
- VMware Workstation
From 17.x · fixed in 17.6.4
- VMware Fusion
From 13.x · fixed in 13.6.4
- VMware Telco Cloud Platform
Version range not reported
- VMware Telco Cloud Infrastructure
Version range not reported