# CVE-2016-2780: Path traversal in n/a

> Local attackers can execute arbitrary code via DLL hijacking in Huawei UTPS due to an untrusted search path vulnerability.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/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:** 13 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vgf5-526g-xhj6

## What is CVE-2016-2780?

CVE-2016-2780 is a high-severity path traversal vulnerability in n/a, published on 13 Apr 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted search path vulnerability in Huawei UTPS before UTPS-V200R003B015D15SP00C983 allows local users to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse DLL in an unspecified directory.

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

It affects 1 product.


Products: Huawei Utps Firmware.

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

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

## Is CVE-2016-2780 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-8769](https://insights.sbomify.com/CVE-2016-8769/): Privilege escalation in Huawei UTPS (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-2780 is a high-severity path traversal vulnerability in n/a, published on 13 Apr 2016. 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-2016-2780 in the wild and no public exploit code.

Affected product: n/a. 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-2780/ (Markdown: https://insights.sbomify.com/CVE-2016-2780/index.md)
```

## Sources

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

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