CVE-2016-9357
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a path traversal (CWE-22) vulnerability in legacy Eaton ePDU web interfaces. An unauthenticated attacker can craft specially designed URLs containing directory traversal sequences (e.g., ../../../) to access sensitive configuration files outside the web root directory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 06-30-2015<= 01-31-2014<= 01-31-2014<= 01-31-2014<= 01-31-2014CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Eaton ePDU devices on the networkScan the network for Eaton Eamxxx, Emaxxx, Eamaxxx, Emaaxx, or Eswaxx Series ePDU devices. Check MAC OUI (Organization Unique Identifier) for Eaton manufacturer prefix or review device inventory/documentation.Affected if Eaton ePDU devices from these series are present on the network.
-
Determine the firmware version and dateAccess the ePDU web interface and navigate to the firmware information page, typically found under 'Device', 'Settings', or 'About' sections. Alternatively, check the SNMP sysDescr or sysVersion OIDs.Affected if Firmware date is 06-30-2015 or earlier for Eamxxx series, or 01-31-2014 or earlier for Emaxxx, Eamaxxx, Emaaxx, or Eswaxx series.
-
Verify the web interface is accessibleAttempt to reach the ePDU web interface via HTTP/HTTPS on the device IP address. Common ports are 80 and 443. Confirm the interface responds with an Eaton login page or API endpoint.Affected if The web interface is exposed and reachable from network segments where the vulnerability can be exploited.
-
Confirm path traversal is exploitable (optional verification)Send a crafted HTTP GET request with directory traversal sequences to access files outside the web root, for example: GET /../../../../etc/passwd or similar paths. Check if the response contains file contents rather than an error.Affected if The request returns sensitive file contents or configuration data from outside the web root directory, confirming the vulnerability is present and exploitable.
A user is affected if they have any Eaton Eamxxx, Emaxxx, Eamaxxx, Emaaxx, or Eswaxx Series ePDU devices running firmware at or below the affected version dates, with the web interface accessible on the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince these products are end-of-life and no longer supported by Eaton, no vendor patches are available. Organizations should remove affected ePDUs from production networks or implement strict network isolation (firewalls/ACLs) to limit exposure; replacement with supported hardware is recommended.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-9357 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data