CVE-2017-4909: VMware Workstation vulnerability

CVE-2017-4909: VMware Workstation (12.x prior to 12.5.3) and Horizon View Client (4.x prior to 4.4.0) contain a heap buffe...

VMware Workstation (12.x prior to 12.5.3) and Horizon View Client (4.x prior to 4.4.0) contain a heap buffer-overflow vulnerability in TrueType Font (TTF) 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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 5, 2024, 14:39 UTC (UTC+00:00)

Security readout for executives and security teams

This is a legacy VMware client-side/host-side memory corruption flaw. If virtual printing is enabled, a compromised guest or View desktop could crash or run code on the Windows machine running VMware Workstation or Horizon View Client. Exposure is most likely on Windows systems still running the affected legacy VMware versions. Horizon View Client is more exposed because virtual printing is enabled by default. Workstation exposure depends on virtual printing being manually enabled. Treat as high priority where legacy VMware clients remain in use, especially Horizon View Client deployments. The business risk is endpoint compromise or disruption through a virtualization feature that may be enabled by default. Mitigation focus: Upgrade Workstation to 12.5.3 or later if affected.; Upgrade Horizon View Client for Windows to 4.4.0 or later if affected.; Disable virtual printing where it is not operationally required..

Prepared: Jun 13, 2026, 04:43 UTC (UTC+00:00)

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.

cve · low confidence lookup

CVE-2017-4909 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: Jun 8, 2017, 13:00 UTC (UTC+00:00)

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

1Source links

CVSS and timeline data

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

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

VMwareWorkstation12.x prior to 12.5.3Listed

VMwareHorizon View Client for Windows4.x prior to 4.4.0Listed

Weakness

CWE details

No CWE listed

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