# CVE-2017-10935: Auth bypass in ZXR10 1800-2S

> Remote authenticated users can bypass password protection to change other users' passwords on ZTE ZXR10 switches.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-f7g7-6hc8-75v5

## What is CVE-2017-10935?

CVE-2017-10935 is a high-severity authentication bypass vulnerability in ZTE ZXR10 1800-2S, published on 25 Jul 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

All versions prior to ZSRV2 V3.00.40 of the ZTE ZXR10 1800-2S products allow remote authenticated users to bypass the original password authentication protection to change other user's password.

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

It affects 1 product.


Products: Zte Zxr10 1800-2s Firmware.

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

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

## Is CVE-2017-10935 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10935 is a high-severity authentication bypass vulnerability in ZTE ZXR10 1800-2S, published on 25 Jul 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10935 in the wild and no public exploit code.

Affected product: ZTE ZXR10 1800-2S. 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-10935/ (Markdown: https://insights.sbomify.com/CVE-2017-10935/index.md)
```

## Sources

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

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