# CVE-2016-9364: Path traversal in Fidelix FX-20 Series Controllers prior to 11.50.19

> Attackers can read arbitrary files on Fidelix FX-20 controllers via path traversal, exposing sensitive server data.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-77wr-wrm7-68v3

## What is CVE-2016-9364?

CVE-2016-9364 is a high-severity path traversal vulnerability in Fidelix FX-20 Series Controllers prior to 11.50.19, 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 Fidelix FX-20 series controllers, versions prior to 11.50.19. Arbitrary file reading via path traversal allows an attacker to access arbitrary files and directories on the server.

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

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

It affects 2 products.


Products: Fidelex Fx-2030a-Basic Firmware, Fidelex Fx-2030a Firmware.

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

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

## Is CVE-2016-9364 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-9364 is a high-severity path traversal vulnerability in Fidelix FX-20 Series Controllers prior to 11.50.19, 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-9364 in the wild and no public exploit code.

Affected product: Fidelix FX-20 Series Controllers prior to 11.50.19. 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-9364/ (Markdown: https://insights.sbomify.com/CVE-2016-9364/index.md)
```

## Sources

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

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