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

> Remote attackers can exploit absolute path traversal in Motorola FX9500 devices to access sensitive files via PL/SQL Server Pages.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 23 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g66m-f6q4-gw56

## What is CVE-2020-10875?

CVE-2020-10875 is a high-severity path traversal vulnerability in n/a, published on 23 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Motorola FX9500 devices allow remote attackers to conduct absolute path traversal attacks, as demonstrated by PL/SQL Server Pages files such as /include/viewtagdb.psp.

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

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

It affects 1 product.


Products: Zebra Fx9500 Firmware.

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

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

## Is CVE-2020-10875 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-32089](https://insights.sbomify.com/CVE-2021-32089/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10875 is a high-severity path traversal vulnerability in n/a, published on 23 Mar 2020. 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-10875 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-10875/ (Markdown: https://insights.sbomify.com/CVE-2020-10875/index.md)
```

## Sources

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

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