dbcve.org
Horizon ViewApplication · VMware

CVE-2017-4907

CRITICAL · 9.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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Unified Access Gateway (2.5.x, 2.7.x, 2.8.x prior to 2.8.1) and Horizon View (7.x prior to 7.1.0, 6.x prior to 6.2.4) contain a heap buffer-overflow vulnerability which may allow a remote attacker to execute code on the security gateway.

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

Heap buffer-overflow vulnerability in VMware Unified Access Gateway and Horizon View security gateway products allows remote attackers to execute arbitrary code by overflowing heap memory buffers. This critical memory corruption vulnerability affects specific versions of both products.

MitigationUpgrade to VMware Unified Access Gateway 2.8.1 or later, Horizon View 7.1.0 or later, or Horizon View 6.2.4 or later to remediate the heap buffer overflow vulnerability.

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:= 6.0= 6.0.2= 6.1= 6.1.1= 6.2= 6.2.1= 6.2.2= 6.2.3= 6.2.4= 7.0
Unified Access GatewayApplication
Affected:= 2.5= 2.5.1= 2.7= 2.7.2= 2.8

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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 if VMware Horizon View is installed
    Check the Windows Programs and Features list, or review the VMware Horizon installation directory for the Connection Server or Security Server components
    Affected if Horizon View is present on the system
  2. Identify if VMware Unified Access Gateway is deployed
    Review network documentation or check the UAG appliance management interface for version information
    Affected if Unified Access Gateway is deployed in the environment
  3. Determine the installed Horizon View version
    Open the VMware Horizon Administrator console, or check the Connection Server installation for the version displayed in Add/Remove Programs or the installation logs
    Affected if The installed version matches exactly: 6.0, 6.0.2, 6.1, 6.1.1, 6.2, 6.2.1, 6.2.2, 6.2.3, 6.2.4, or 7.0
  4. Determine the installed Unified Access Gateway version
    Access the UAG admin portal or check the appliance system information for the exact version number
    Affected if The installed version matches exactly: 2.5, 2.5.1, 2.7, 2.7.2, or 2.8

The environment is affected if either VMware Horizon View version 6.0 through 7.0 (excluding 7.1+) or VMware Unified Access Gateway version 2.5 through 2.8 (excluding 2.8.1+) is installed and the security gateway component is exposed to network access.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to VMware Unified Access Gateway 2.8.1 or later, Horizon View 7.1.0 or later, or Horizon View 6.2.4 or later to remediate the heap buffer overflow vulnerability.

Recommended fix High confidence

Horizon View 6.2.4+ / 7.1.0+; Unified Access Gateway 2.8.1+

  1. Identify which Horizon View or Unified Access Gateway version is currently deployed
  2. For Horizon View 6.x deployments: Upgrade to version 6.2.4 or later
  3. For Horizon View 7.x deployments: Upgrade to version 7.1.0 or later
  4. For Unified Access Gateway 2.5.x/2.7.x/2.8.x deployments: Upgrade to version 2.8.1 or later
  5. After upgrade, verify the vulnerability is resolved by checking VMware security advisories
Caveat Review VMware release notes for breaking changes between versions; test upgrade in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Horizon View Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-4907 — 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-4907 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