# CVE-2018-12031: Path traversal in n/a

> An attacker can read arbitrary local files via directory traversal in the firmware download action of Eaton Intelligent Power Manager.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2v4v-8555-8jp6

## What is CVE-2018-12031?

CVE-2018-12031 is a critical path traversal vulnerability in n/a, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Local file inclusion in Eaton Intelligent Power Manager v1.6 allows an attacker to include a file via server/node_upgrade_srv.js directory traversal with the firmware parameter in a downloadFirmware action.

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

## Which versions are affected by CVE-2018-12031?

It affects 1 product.


Products: Eaton Intelligent Power Manager.

## How do I fix CVE-2018-12031?

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

## Is CVE-2018-12031 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-12031 exists.

Public exploit code:

- CVE-2018-12031 | LFI in Eaton Intelligent Power Manager  v1.6 allows an attacker to include a file, it can lead to sensitive information disclosure, denial of service and code execution. (github_poc): https://github.com/EmreOvunc/Eaton-Intelligent-Power-Manager-Local-File-Inclusion
- Eaton Intelligent Power Manager 1.6 - Directory Traversal (nuclei): http/cves/2018/CVE-2018-12031.yaml

## Other vulnerabilities in n/a

- [CVE-2021-23281](https://insights.sbomify.com/CVE-2021-23281/): Remote Code execution (critical 10.0)
- [CVE-2020-6651](https://insights.sbomify.com/CVE-2020-6651/): Command injection via specially crafted file name during config file upload (high 8.8)
- [CVE-2021-23278](https://insights.sbomify.com/CVE-2021-23278/): Arbitrary File delete (high 8.7)
- [CVE-2021-23277](https://insights.sbomify.com/CVE-2021-23277/): Improper Neutralization of Directives in Dynamically Evaluated Code (high 8.3)
- [CVE-2021-23279](https://insights.sbomify.com/CVE-2021-23279/): Arbitrary File delete (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12031 and fix it if it is affected.

What it is: CVE-2018-12031 is a critical path traversal vulnerability in n/a, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-12031 exists.

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-2018-12031/ (Markdown: https://insights.sbomify.com/CVE-2018-12031/index.md)
```

## Sources

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

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