# CVE-2016-9357: Path traversal in Eaton ePDU EoL devices

> Unauthenticated attackers can access configuration files via path traversal in legacy Eaton ePDU devices, which are end-of-life and unsupported.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4r8r-4jfr-7g35

## What is CVE-2016-9357?

CVE-2016-9357 is a medium-severity path traversal vulnerability in Eaton ePDU EoL devices, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in certain legacy Eaton ePDUs -- the affected products are past end-of-life (EoL) and no longer supported: EAMxxx prior to June 30, 2015, EMAxxx prior to January 31, 2014, EAMAxx prior to January 31, 2014, EMAAxx prior to January 31, 2014, and ESWAxx prior to January 31, 2014. An unauthenticated attacker may be able to access configuration files with a specially crafted URL (Path Traversal).

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

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

It affects 5 products.


Products: Eaton Eamaxx Series Epdu Firmware, Eaton Eamxxx Series Epdu Firmware, Eaton Emaaxx Series Epdu Firmware, Eaton Emaxxx Series Epdu Firmware, Eaton Eswaxx Series Epdu Firmware.

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

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

## Is CVE-2016-9357 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-9357 is a medium-severity path traversal vulnerability in Eaton ePDU EoL devices, published on 13 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-9357 in the wild and no public exploit code.

Affected product: Eaton ePDU EoL devices. 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-9357/ (Markdown: https://insights.sbomify.com/CVE-2016-9357/index.md)
```

## Sources

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

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