# CVE-2020-6866: Denial of service in ZXCTN 6500

> An attacker can cause a denial of service on ZTE ZXCTN 6500 network devices by issuing a specific command due to a resource management error.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/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:** 30 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7mch-5p8p-x68j

## What is CVE-2020-6866?

CVE-2020-6866 is a medium-severity denial of service vulnerability in ZXCTN 6500, published on 30 Apr 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A ZTE product is impacted by a resource management error vulnerability. An attacker could exploit this vulnerability to cause a denial of service by issuing a specific command. This affects: ZXCTN 6500 version V2.10.00R3B87.

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

It affects 1 product.


Products: Zte Zxctn 6500 Firmware.

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

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

## Is CVE-2020-6866 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6866 is a medium-severity denial of service vulnerability in ZXCTN 6500, published on 30 Apr 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6866 in the wild and no public exploit code.

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

## Sources

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

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