dbcve.org
Horizon ViewApplication · VMware

CVE-2017-4913

HIGH · 7.8 CVSS v3.0 Published 2017-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
VMware Workstation (12.x prior to 12.5.3) and Horizon View Client (4.x prior to 4.4.0) contain an integer-overflow vulnerability in the True Type Font 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Integer overflow vulnerability in the True Type Font parser (TPView.dll) in VMware Workstation 12.x before 12.5.3 and Horizon View Client 4.x before 4.4.0. The flaw can be triggered when parsing malicious TTF files via the virtual printing feature, potentially allowing a guest VM or View desktop to execute arbitrary code or cause a denial of service on the host Windows system.

MitigationUpgrade to VMware Workstation 12.5.3 or later, or Horizon View Client 4.4.0 or later. Alternatively, disable the virtual printing feature if not required, as exploitation is only possible when this feature is enabled.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Horizon ViewApplication
Affected:= 4.0= 4.1= 4.2= 4.3
WorkstationApplication
Affected:= 12.0= 12.0.1= 12.1= 12.1.1= 12.5= 12.5.1= 12.5.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed VMware product
    Open the application - for Workstation go to Help > About VMware Workstation; for Horizon View check the client interface or Windows Programs and Features
    Affected if The product is VMware Workstation 12.x or VMware Horizon View Client 4.x (versions 4.0-4.3)
  2. Check Workstation version
    In VMware Workstation, go to Help > About VMware Workstation and note the full version number displayed
    Affected if Version is 12.0, 12.0.1, 12.1, 12.1.1, 12.5, 12.5.1, or 12.5.2 (versions before 12.5.3 are affected)
  3. Check Horizon View Client version
    In Horizon View Client, go to Help > About VMware Horizon Client or check the version in the Windows Programs and Features list
    Affected if Version is 4.0, 4.1, 4.2, or 4.3 (versions before 4.4.0 are affected)
  4. Verify virtual printing feature status
    In VMware Workstation, go to Edit > Preferences > Printing and confirm if 'Enable virtual printing' is checked; in Horizon View check the client settings for printing configuration
    Affected if Virtual printing is enabled - this feature must be active for the vulnerability to be exploitable

You are affected if you have VMware Workstation 12.x (any version before 12.5.3) or Horizon View Client 4.0-4.3 AND the virtual printing feature is turned on.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to VMware Workstation 12.5.3 or later, or Horizon View Client 4.4.0 or later. Alternatively, disable the virtual printing feature if not required, as exploitation is only possible when this feature is enabled.

Fix this in Horizon View Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-4913 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-4913 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data