# CVE-2016-6593: Code injection in VIP Access Desktop

> Local attackers can execute arbitrary code during startup due to untrusted search path in Symantec VIP Access Desktop.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7g77-97mx-6jpp

## What is CVE-2016-6593?

CVE-2016-6593 is a high-severity code injection vulnerability in Symantec VIP Access Desktop, published on 8 Jan 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A code-execution vulnerability exists during startup in jhi.dll and otpiha.dll in Symantec VIP Access Desktop before 2.2.2, which could let local malicious users execute arbitrary code.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2016-6593?

It affects 1 product.


Products: Symantec Vip Access Desktop.

## How do I fix CVE-2016-6593?

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

## Is CVE-2016-6593 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6593 and fix it if it is affected.

What it is: CVE-2016-6593 is a high-severity code injection vulnerability in Symantec VIP Access Desktop, published on 8 Jan 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-6593 in the wild and no public exploit code.

Affected product: Symantec VIP Access Desktop. 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-2016-6593/ (Markdown: https://insights.sbomify.com/CVE-2016-6593/index.md)
```

## Sources

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

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