# CVE-2017-15583: Path traversal in n/a

> An attacker can retrieve arbitrary files from the ABB Fox515T embedded web server due to lack of filename validation in the file inclusion parameter.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 18 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h98c-73gp-34gh

## What is CVE-2017-15583?

CVE-2017-15583 is a medium-severity path traversal vulnerability in n/a, published on 18 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The embedded web server on ABB Fox515T 1.0 devices is vulnerable to Local File Inclusion. It accepts a parameter that specifies a file for display or for use as a template. The filename is not validated; an attacker could retrieve any file.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Hitachienergy Fox515t Firmware.

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

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

## Is CVE-2017-15583 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-14025](https://insights.sbomify.com/CVE-2017-14025/): Path traversal in ABB FOX515T (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15583 is a medium-severity path traversal vulnerability in n/a, published on 18 Oct 2017. 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-15583 in the wild and no public exploit code.

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

## Sources

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

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