# CVE-2019-16105: Path traversal in n/a

> An attacker can exploit a directory traversal vulnerability in the Silver Peak EdgeConnect SD-WAN API to read arbitrary files from the system.

- **Severity:** Medium 4.9 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-924p-5rrh-2wjw

## What is CVE-2019-16105?

CVE-2019-16105 is a medium-severity path traversal vulnerability in n/a, published on 8 Sep 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Silver Peak EdgeConnect SD-WAN before 8.1.7.x allows ..%2f directory traversal via a rest/json/configdb/download/ URI.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2019-16105?

It affects 1 product.


Products: Silver-Peak Unity Edgeconnect Sd-Wan Firmware.

## How do I fix CVE-2019-16105?

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

## Is CVE-2019-16105 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16102](https://insights.sbomify.com/CVE-2019-16102/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2019-16099](https://insights.sbomify.com/CVE-2019-16099/): Silver Peak EdgeConnect SD-WAN before 8.1.7.x allows CSRF via JSON data to a .swf file. (high 8.8)
- [CVE-2019-16100](https://insights.sbomify.com/CVE-2019-16100/): Denial of service in n/a (high 7.5)
- [CVE-2019-16103](https://insights.sbomify.com/CVE-2019-16103/): Privilege escalation in n/a (high 7.2)
- [CVE-2019-16104](https://insights.sbomify.com/CVE-2019-16104/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16105 and fix it if it is affected.

What it is: CVE-2019-16105 is a medium-severity path traversal vulnerability in n/a, published on 8 Sep 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-16105 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-2019-16105/ (Markdown: https://insights.sbomify.com/CVE-2019-16105/index.md)
```

## Sources

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

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