# CVE-2020-6870: Auth bypass in NetNumenU31R20

> An attacker can bypass authentication to log into the FTP server, allowing them to tamper with passwords and manipulate files on the network management system.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-93v6-m8fp-hm8p

## What is CVE-2020-6870?

CVE-2020-6870 is a high-severity authentication bypass vulnerability in ZTE NetNumenU31R20, published on 24 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The version V12.17.20T115 of ZTE U31R20 product is impacted by a design error vulnerability. An attacker could exploit the vulnerability to log in to the FTP server to tamper with the password, and illegally download, modify, upload, or delete files, causing improper operation of the network management system and equipment. This affects: NetNumenU31R20 V12.17.20T115

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

It affects 1 product.


Products: Zte Netnumen U31 R10 Firmware.

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

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

## Is CVE-2020-6870 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6870 is a high-severity authentication bypass vulnerability in ZTE NetNumenU31R20, published on 24 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6870 in the wild and no public exploit code.

Affected product: ZTE NetNumenU31R20. 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-6870/ (Markdown: https://insights.sbomify.com/CVE-2020-6870/index.md)
```

## Sources

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

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