Zxa10 C350m FirmwareOperating system · Zte

CVE-2022-39070

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-22
Fix available
A fix is available. Upgrade to 2.1.0xgp002.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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
There is an access control vulnerability in some ZTE PON OLT products. Due to improper access control settings, remote attackers could use the vulnerability to log in to the device and execute any operation.

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

Access control vulnerability in ZTE PON OLT (Passive Optical Network Optical Line Terminal) devices allowing remote unauthenticated attackers to log in and execute arbitrary operations due to improper access control settings. The vulnerability enables full device compromise without authentication.

MitigationImplement proper access control by restricting management interface exposure, disabling default credentials, enforcing strong authentication, and applying vendor-supplied patches. Network segmentation should be used to limit OLT management plane exposure.

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
Zxa10 C350m FirmwareOperating system
Affected:>= 2.1.0, < 2.1.0xgp002.4
Zxa10 C300m FirmwareOperating system
Affected:>= 2.1.0, < 2.1.0xgp002.4

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
High
Integrity
High
Availability
High

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

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 the device model
    Log into the OLT device CLI or web interface and retrieve the hardware model information using 'show version' command or checking the system information page
    Affected if The device is not a ZTE Zxa10 C350m or Zxa10 C300m PON OLT, as only these models are affected
  2. Check the firmware version
    Execute 'show version' or 'show firmware' command in the device CLI to retrieve the currently installed firmware version
    Affected if The firmware version is greater than or equal to 2.1.0 AND less than 2.1.0xgp002.4, meaning the device is within the vulnerable version range
  3. Verify management interface accessibility
    Check network configuration to determine if the management interface (HTTP/HTTPS/SSH/Telnet) is exposed to untrusted networks or the internet. Review the interface binding settings and ACL configurations using 'show ip interface' or similar commands
    Affected if The management interface is accessible from unauthenticated or untrusted network segments without proper firewall or ACL restrictions
  4. Inspect access control configuration
    Review the device's access control settings by examining the AAA configuration, user authentication settings, and privilege levels using commands like 'show running-config | include aaa' or 'show user'
    Affected if Default or weak authentication is configured, or authentication enforcement is disabled for management access

A user is affected if they have a ZTE Zxa10 C350m or C300m device running firmware version 2.1.0 through 2.1.0xgp002.3 with its management interface exposed to untrusted networks or with improper access control settings.

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 2.1.0xgp002.4 or later
Fixed in 2.1.0xgp002.4
Interim mitigation

Implement proper access control by restricting management interface exposure, disabling default credentials, enforcing strong authentication, and applying vendor-supplied patches. Network segmentation should be used to limit OLT management plane exposure.

Recommended fix High confidence

Zxa10 C350m/C300m firmware version 2.1.0xgp002.4 or later

  1. 1. Identify the current firmware version of the Zxa10 C350m or C300m device by accessing the device CLI or web management interface.
  2. 2. Navigate to ZTE technical support portal (support.zte.com.cn) and locate the firmware download section for the specific device model.
  3. 3. Download firmware version 2.1.0xgp002.4 or later for your device model.
  4. 4. Access the device web management interface or CLI with administrative credentials.
  5. 5. Upload the new firmware file following the standard ZTE firmware upgrade procedure (typically via the 'System Maintenance' > 'Firmware Upgrade' section in web GUI or via CLI upgrade command).
  6. 6. Wait for the firmware upload and installation to complete - do not power off the device during this process.
  7. 7. After reboot, verify the device is running firmware version 2.1.0xgp002.4 or later.
  8. 8. Verify that normal device operations and services are functioning properly.
Caveat Standard firmware upgrade caveats apply - ensure backup of configuration before upgrade and verify compatibility with existing network services

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

Fix this in Zxa10 C350m Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-39070 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