Guest VM interruption via VMCI memory leak
Published May 29, 2020 · Updated Aug 4, 2024
Memory leak in the VMCI module in VMware ESXi, Workstation, and Fusion allows local users to crash a virtual machine's VMX process. The VMCI module fails to release memory during an undisclosed guest operation; VMware has not identified the affected function or input. The attacker requires non-administrative access inside a guest, and exploitation interrupts only that virtual machine by terminating its VMX process.
Summary
What happened
Memory leak in the VMCI module in VMware ESXi, Workstation, and Fusion allows local users to crash a virtual machine's VMX process. The VMCI module fails to release memory during an undisclosed guest operation; VMware has not identified the affected function or input. The attacker requires non-administrative access inside a guest, and exploitation interrupts only that virtual machine by terminating its VMX process.
The record
- CVE
- CVE-2020-3959
- Published
- May 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- VMware
- Product
- VMware Workstation
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 29, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=15.x before 15.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo