dbcve.org
Zxen Cg200 FirmwareOperating system · Zte

CVE-2022-23142

MEDIUM · 5.3 CVSS v3.1 Published 2022-07-18
Fix available
A fix is available. Upgrade to 1.0.0p1n6_m or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Denial-of-service vulnerability in ZXEN CG200 network device management web interface. Attackers can send rapid HTTP GET requests to exhaust server resources, rendering the product management websites inaccessible.

MitigationImplement rate limiting on the management interface, apply available firmware updates from ZXEN, or deploy network-level filtering/WAF to block abnormal request volumes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Zxen Cg200 FirmwareOperating system
Affected:< 1.0.0p1n6_m

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the device CLI or web interface and retrieve the model identifier. This is typically displayed on the login page, in system information, or via CLI command 'show system-info' or 'show version'.
    Affected if Device is not a ZXEN CG200 model, then not affected by this specific CVE.
  2. Check firmware version
    In the device web interface, navigate to System > Firmware or System > Version. Alternatively, use CLI command 'show version' or 'show firmware-version' to retrieve the installed firmware version number.
    Affected if Firmware version is 1.0.0p1n6_m or higher - NOT vulnerable. Firmware version is below 1.0.0p1n6_m - POTENTIALLY VULNERABLE.
  3. Verify management web interface is enabled
    In the device web interface, check System > Management > HTTP/HTTPS settings. Confirm the management web service is enabled. Also check if the interface is accessible from external networks via LAN/WAN ports.
    Affected if Management web interface is disabled or only accessible from isolated management VLAN - attack surface is reduced. Interface is enabled and network-accessible - vulnerable to exploitation.
  4. Check for resource exhaustion symptoms
    Monitor device performance via CLI: 'show system-resources' or 'show cpu usage'. Look for unusually high CPU or memory usage. Check web server process status with 'show processes http' or similar. Review system logs for 'out of memory' or 'service unavailable' errors.
    Affected if Device shows high resource usage or HTTP service errors without other cause - may indicate exploitation of this DoS vulnerability.

Device is affected if it is a ZXEN CG200 running firmware version below 1.0.0p1n6_m AND the management web interface is enabled and network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.0p1n6_m or later
Fixed in 1.0.0p1n6_m
Interim mitigation

Implement rate limiting on the management interface, apply available firmware updates from ZXEN, or deploy network-level filtering/WAF to block abnormal request volumes.

Recommended fix Moderate confidence

Upgrade to firmware version 1.0.0p1n6_m or later

  1. 1. Contact ZXEN technical support at support.zte.com.cn to obtain the fixed firmware version 1.0.0p1n6_m or later.
  2. 2. Download the firmware update package from the official support portal.
  3. 3. Review the firmware upgrade instructions specific to the CG200 device.
  4. 4. Backup the current device configuration before performing the upgrade.
  5. 5. Upload and install the new firmware version 1.0.0p1n6_m via the device management interface.
  6. 6. After upgrade, verify that the device management web interface remains accessible under high request loads.
  7. 7. Confirm the firmware version has been updated successfully.
Caveat Review release notes for any configuration changes required after upgrade; firmware upgrades may require reconfiguration of some settings

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zxen Cg200 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23142 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data