# CVE-2017-10933: Path traversal in ZXDT22 SF01

> Remote attackers can read arbitrary files on ZTE ZXDT22 SF01 energy monitoring systems via directory traversal.

- **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:** 19 Oct 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4w78-w35x-w85p

## What is CVE-2017-10933?

CVE-2017-10933 is a high-severity path traversal vulnerability in ZTE ZXDT22 SF01, published on 19 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions prior to V2.06.00.00 of ZTE ZXDT22 SF01, an monitoring system of ZTE energy product, are impacted by directory traversal vulnerability that allows remote attackers to read arbitrary files on the system via a full path name after host address.

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

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

It affects 1 product.


Products: Zte Zxdt22 Sf01 Firmware.

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

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

## Is CVE-2017-10933 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10933 is a high-severity path traversal vulnerability in ZTE ZXDT22 SF01, published on 19 Oct 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-2017-10933 in the wild and no public exploit code.

Affected product: ZTE ZXDT22 SF01. 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-10933/ (Markdown: https://insights.sbomify.com/CVE-2017-10933/index.md)
```

## Sources

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

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