# CVE-2017-15550: Path traversal in EMC Avamar Server 7.1.x, 7.2.x, 7.3.x, 7.4.x, 7.5.0, EMC NetWorker Virtual Edition (NVE) 9.0.x, 9.1.x, 9.2.x, EMC Integrated Data Protection Appliance 2.0

> Remote authenticated low-privilege users can read arbitrary files on the server file system via path traversal in EMC data protection products.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vvxv-5mj6-r356

## What is CVE-2017-15550?

CVE-2017-15550 is a high-severity path traversal vulnerability in EMC Avamar Server 7.1.x, 7.2.x, 7.3.x, 7.4.x, 7.5.0, EMC NetWorker Virtual Edition (NVE) 9.0.x, 9.1.x, 9.2.x, EMC Integrated Data Protection Appliance 2.0, published on 5 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in EMC Avamar Server 7.1.x, 7.2.x, 7.3.x, 7.4.x, 7.5.0; EMC NetWorker Virtual Edition (NVE) 9.0.x, 9.1.x, 9.2.x; and EMC Integrated Data Protection Appliance 2.0. A remote authenticated malicious user with low privileges could access arbitrary files on the server file system in the context of the running vulnerable application via Path traversal.

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

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

It affects 3 products.


Products: Emc Avamar Server, Emc Integrated Data Protection Appliance, Emc Networker.

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

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

## Is CVE-2017-15550 being exploited?

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

## Other vulnerabilities in EMC Avamar Server 7.1.x, 7.2.x, 7.3.x, 7.4.x, 7.5.0, EMC NetWorker Virtual Edition (NVE) 9.0.x, 9.1.x, 9.2.x, EMC Integrated Data Protection Appliance 2.0

- [CVE-2017-15548](https://insights.sbomify.com/CVE-2017-15548/): Auth bypass in EMC Avamar Server 7.1.x, 7.2.x, 7.3.x, 7.4.x, 7.5.0, EMC NetWorker Virtual Edition (NVE) 9.0.x, 9.1.x, 9.2.x, EMC Integrated Data Protection Appliance 2.0 (critical 9.8)
- [CVE-2017-4989](https://insights.sbomify.com/CVE-2017-4989/): Auth bypass in EMC Avamar Server Software 7.3.1-125, 7.3.0-233, 7.3.0-226, 7.2.1-32, 7.2.1-31, 7.2.0-401 (critical 9.8)
- [CVE-2017-4990](https://insights.sbomify.com/CVE-2017-4990/): File upload in EMC Avamar Server Software 7.4.1-58, 7.4.0-242, 7.3.1-125, 7.3.0-233, 7.3.0-226 (critical 9.8)
- [CVE-2016-0903](https://insights.sbomify.com/CVE-2016-0903/): Auth bypass in n/a (critical 9.1)
- [CVE-2013-3274](https://insights.sbomify.com/CVE-2013-3274/): Missing authorization in n/a (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15550 is a high-severity path traversal vulnerability in EMC Avamar Server 7.1.x, 7.2.x, 7.3.x, 7.4.x, 7.5.0, EMC NetWorker Virtual Edition (NVE) 9.0.x, 9.1.x, 9.2.x, EMC Integrated Data Protection Appliance 2.0, published on 5 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15550 in the wild and no public exploit code.

Affected product: EMC Avamar Server 7.1.x, 7.2.x, 7.3.x, 7.4.x, 7.5.0, EMC NetWorker Virtual Edition (NVE) 9.0.x, 9.1.x, 9.2.x, EMC Integrated Data Protection Appliance 2.0. 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-15550/ (Markdown: https://insights.sbomify.com/CVE-2017-15550/index.md)
```

## Sources

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

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