# CVE-2017-4911: Memory corruption in Horizon View Client for Windows

> Out-of-bounds write in JPEG2000 parser allows guest code execution or DoS on host if virtual printing is enabled.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rx5v-pch7-54c3

## What is CVE-2017-4911?

CVE-2017-4911 is a high-severity memory corruption vulnerability in Vmware Workstation, published on 8 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

VMware Workstation (12.x prior to 12.5.3) and Horizon View Client (4.x prior to 4.4.0) contain multiple out-of-bounds write vulnerabilities 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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2017-4911?

It affects 2 products.


Products: Vmware Horizon View, Vmware Workstation.

## How do I fix CVE-2017-4911?

No fix has been published for CVE-2017-4911 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-4911 being exploited?

There is no known exploitation of CVE-2017-4911 in the wild and no public exploit code.

## Other vulnerabilities in Vmware Workstation

- [CVE-2017-4907](https://insights.sbomify.com/CVE-2017-4907/): Memory corruption in Horizon View (critical 9.8)
- [CVE-2017-4918](https://insights.sbomify.com/CVE-2017-4918/): Command injection in Horizon View Client for Mac (critical 9.8)
- [CVE-2017-4935](https://insights.sbomify.com/CVE-2017-4935/): Memory corruption in Horizon View Client for Windows (high 7.8)
- [CVE-2017-4936](https://insights.sbomify.com/CVE-2017-4936/): Memory corruption in Horizon View Client for Windows (high 7.8)
- [CVE-2017-4937](https://insights.sbomify.com/CVE-2017-4937/): Memory corruption in Horizon View Client for Windows (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-4911 and fix it if it is affected.

What it is: CVE-2017-4911 is a high-severity memory corruption vulnerability in Vmware Workstation, published on 8 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-4911 in the wild and no public exploit code.

Affected product: Vmware Workstation. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-4911/ (Markdown: https://insights.sbomify.com/CVE-2017-4911/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-4911
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-4911
- OSV: https://osv.dev/vulnerability/CVE-2017-4911

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-4911/
Summaries are generated and may contain mistakes; the official description above is the record.