CVE-2017-4933: VMware ESXi vulnerability
VMware · ESXi
Affected: VMware ESXi · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 89% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
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.
Affected products3
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- VMware · ESXi6.5 before ESXi650-201710401-BG
- VMware · Workstation12.x before 12.5.8
- VMware · Fusion8.x before 8.5.9
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- VMware
- Published
- December 2017
CoverageNo articles yet
No CyberSIXT article names CVE-2017-4933 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.