# CVE-2020-17383: Path traversal in n/a

> Unauthenticated attackers can exploit directory traversal to gain root access and read sensitive configuration data and passwords on Telos Z/IP One devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 24 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-72j5-838x-5995

## What is CVE-2020-17383?

CVE-2020-17383 is a critical path traversal vulnerability in n/a, published on 24 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A directory traversal vulnerability on Telos Z/IP One devices through 4.0.0r grants an unauthenticated individual root level access to the device's file system. This can be used to identify configuration settings, password hashes for built-in accounts, and the cleartext password for remote configuration of the device through the WebUI.

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

## Which versions are affected by CVE-2020-17383?

It affects 1 product.


Products: Telosalliance Z\/Ip One Firmware.

## How do I fix CVE-2020-17383?

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

## Is CVE-2020-17383 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-17383 and fix it if it is affected.

What it is: CVE-2020-17383 is a critical path traversal vulnerability in n/a, published on 24 Jan 2022. 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-2020-17383 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-2020-17383/ (Markdown: https://insights.sbomify.com/CVE-2020-17383/index.md)
```

## Sources

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

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