# CVE-2020-6867: Denial of service in ZENIC ONE R22b

> Frequent RPC calls under heavy traffic cause long unresponsiveness and memory overflow in ZTE SDON controllers, leading to denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 30 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w2gh-fr9p-56v5

## What is CVE-2020-6867?

CVE-2020-6867 is a medium-severity denial of service vulnerability in ZENIC ONE R22b, published on 30 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ZTE's SDON controller is impacted by the resource management error vulnerability. When RPC is frequently called by other applications in the case of mass traffic data in the system, it will result in no response for a long time and memory overflow risk. This affects: ZENIC ONE R22b versions V16.19.10P02SP002 and V16.19.10P02SP005.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Zte Zenic One R22b.

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

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

## Is CVE-2020-6867 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6867 is a medium-severity denial of service vulnerability in ZENIC ONE R22b, published on 30 Apr 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-6867 in the wild and no public exploit code.

Affected product: ZENIC ONE R22b. 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-6867/ (Markdown: https://insights.sbomify.com/CVE-2020-6867/index.md)
```

## Sources

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

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