# CVE-2022-23142: Denial of service in ZXEN CG200

> An attacker can cause a denial of service on the ZXEN CG200 management interface by flooding it with HTTP GET requests.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-p3fr-37g5-xgq2

## What is CVE-2022-23142?

CVE-2022-23142 is a medium-severity denial of service vulnerability in ZXEN CG200, published on 18 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZXEN CG200 has a DoS vulnerability. An attacker could construct and send a large number of HTTP GET requests in a short time, which can make the product management websites not accessible.

## Which versions are affected by CVE-2022-23142?

It affects 1 product.


Products: Zte Zxen Cg200 Firmware.

## How do I fix CVE-2022-23142?

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

## Is CVE-2022-23142 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23142 and fix it if it is affected.

What it is: CVE-2022-23142 is a medium-severity denial of service vulnerability in ZXEN CG200, published on 18 Jul 2022. 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-2022-23142 in the wild and no public exploit code.

Affected product: ZXEN CG200. 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-2022-23142/ (Markdown: https://insights.sbomify.com/CVE-2022-23142/index.md)
```

## Sources

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

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