# CVE-2016-8211: Path traversal in EMC Data Protection Advisor EMC Data Protection Advisor 6.1.x, EMC Data Protection Advisor 6.2, EMC Data Protection Advisor 6.2.1, EMC Data Protection Advisor 6.2.2, EMC Data Protection Advisor 6.2.3 prior to patch 446

> Malicious users can exploit a path traversal vulnerability in EMC Data Protection Advisor to compromise the affected system.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-97hr-w4x9-qrwp

## What is CVE-2016-8211?

CVE-2016-8211 is a high-severity path traversal vulnerability in EMC Data Protection Advisor EMC Data Protection Advisor 6.1.x, EMC Data Protection Advisor 6.2, EMC Data Protection Advisor 6.2.1, EMC Data Protection Advisor 6.2.2, EMC Data Protection Advisor 6.2.3 prior to patch 446, published on 3 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EMC Data Protection Advisor 6.1.x, EMC Data Protection Advisor 6.2, EMC Data Protection Advisor 6.2.1, EMC Data Protection Advisor 6.2.2, EMC Data Protection Advisor 6.2.3 prior to patch 446 has a path traversal vulnerability that may potentially be exploited by malicious users to compromise the affected system.

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

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

It affects 1 product.


Products: Dell Emc Data Protection Advisor.

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

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

## Is CVE-2016-8211 being exploited?

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

## Other vulnerabilities in EMC Data Protection Advisor EMC Data Protection Advisor 6.1.x, EMC Data Protection Advisor 6.2, EMC Data Protection Advisor 6.2.1, EMC Data Protection Advisor 6.2.2, EMC Data Protection Advisor 6.2.3 prior to patch 446

- [CVE-2019-18581](https://insights.sbomify.com/CVE-2019-18581/): Missing authorization in Data Protection Advisor (critical 9.1)
- [CVE-2019-18582](https://insights.sbomify.com/CVE-2019-18582/): Code injection in Data Protection Advisor (critical 9.1)
- [CVE-2020-5352](https://insights.sbomify.com/CVE-2020-5352/): Command injection in Data Protection Advisor (high 8.8)
- [CVE-2018-11048](https://insights.sbomify.com/CVE-2018-11048/): XML external entity in Data Protection Advisor (high 8.1)
- [CVE-2020-5351](https://insights.sbomify.com/CVE-2020-5351/): Hardcoded credentials in Data Protection Advisor (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8211 is a high-severity path traversal vulnerability in EMC Data Protection Advisor EMC Data Protection Advisor 6.1.x, EMC Data Protection Advisor 6.2, EMC Data Protection Advisor 6.2.1, EMC Data Protection Advisor 6.2.2, EMC Data Protection Advisor 6.2.3 prior to patch 446, published on 3 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-8211 in the wild and no public exploit code.

Affected product: EMC Data Protection Advisor EMC Data Protection Advisor 6.1.x, EMC Data Protection Advisor 6.2, EMC Data Protection Advisor 6.2.1, EMC Data Protection Advisor 6.2.2, EMC Data Protection Advisor 6.2.3 prior to patch 446. 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-8211/ (Markdown: https://insights.sbomify.com/CVE-2016-8211/index.md)
```

## Sources

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

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