CVE-2017-4935 json
VMware Workstation (12.x before 12.5.8) and Horizon View Client for Windows (4.x before 4.6.1) contain an out-of-bounds write vulnerability…
published 2017-11-17 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-14052
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
VMware Workstation (12.x before 12.5.8) and Horizon View Client for Windows (4.x before 4.6.1) contain an out-of-bounds write vulnerability in JPEG2000 parser in the TPView.dll. On Workstation, this may allow a guest to execute code or perform a Denial of Service on the Windows OS that runs Workstation. In the case of a Horizon View Client, this may allow a View desktop to execute code or perform a Denial of Service on the Windows OS that runs the Horizon View Client. Exploitation is only possible if virtual printing has been enabled. This feature is not enabled by default on Workstation but it is enabled by default on Horizon View Client.
Patch / fix
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 6.9 | AV:L/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- VMware Workstation
- VMware Horizon View Client for Windows
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
- Technology feeds
References
-
vmware.com
/security/advisories/VMSA-2017-0018.html
patch, vendor-advisory
-
securitytracker.com
/id/1039836
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1039835
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/101902
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-4935
- NVD CVE-2017-4935
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.