CVE-2017-4933 Memory corruption in ESXi
An authenticated VNC user can trigger a heap overflow to execute arbitrary code within a virtual machine, requiring manual VNC configuration.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2017-4933?
CVE-2017-4933 is a high-severity memory corruption vulnerability in Vmware Esxi, published on 20 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
VMware ESXi (6.5 before ESXi650-201710401-BG), Workstation (12.x before 12.5.8), and Fusion (8.x before 8.5.9) contain a vulnerability that could allow an authenticated VNC session to cause a heap overflow via a specific set of VNC packets resulting in heap corruption. Successful exploitation of this issue could result in remote code execution in a virtual machine via the authenticated VNC session. Note: In order for exploitation to be possible in ESXi, VNC must be manually enabled in a virtual machine's .vmx configuration file. In addition, ESXi must be configured to allow VNC traffic through the built-in firewall.
Weakness: CWE-787
Which versions are affected by CVE-2017-4933?
It affects 3 products.
Products include Vmware Esxi, Vmware Fusion, Vmware Workstation Pro.
How do I fix CVE-2017-4933?
No fix has been published for CVE-2017-4933 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2017-4933 being exploited?
There is no known exploitation of CVE-2017-4933 in the wild and no public exploit code.
Other vulnerabilities in Vmware Esxi
Sources
Also known as GHSA-6m9x-2xwm-463c.