LiveActive security incident?Get immediate response
CVE Record

CVE-2017-4933: VMware ESXi (6.5 before ESXi650-201710401-BG), Workstation (12.x before 12.5.8), and Fusion (8.x before 8.5...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2017-4933 affects older VMware ESXi, Workstation, and Fusion releases. An attacker with an authenticated VNC session to a virtual machine could trigger memory corruption and potentially run code inside that VM. ESXi exposure is narrower because VNC must be manually enabled and allowed through the ESXi firewall. Most exposure is in environments still running the affected VMware versions with VM console VNC enabled or reachable. ESXi is exposed only when VNC is manually enabled in a VM's .vmx file and the built-in firewall permits VNC traffic. Treat this as priority patching for VMware systems that expose VM VNC access. Systems without VNC enabled have lower immediate exposure, but unsupported or outdated VMware installations should still be remediated through normal vulnerability management. Mitigation focus: Upgrade ESXi 6.5 to include ESXi650-201710401-BG or later vendor-fixed builds.; Upgrade Workstation 12.x to 12.5.8 or later.; Upgrade Fusion 8.x to 8.5.9 or later..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-4933 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
VMwareESXi6.5 before ESXi650-201710401-BGListed
VMwareWorkstation12.x before 12.5.8Listed
VMwareFusion8.x before 8.5.9Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.