dbcve.org
Otcp FirmwareOperating system · Zte

CVE-2022-23143

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-05
Fix available
A fix is available. Upgrade to 2.21.40.06 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
ZTE OTCP product is impacted by a permission and access control vulnerability. Due to improper permission settings, an attacker with high permissions could use this vulnerability to maliciously delete and modify files.

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

This is an access control vulnerability in ZTE OTCP where improper permission settings allow authenticated attackers with high privileges to maliciously delete and modify files on the system. The vulnerability stems from insufficient authorization controls that fail to properly restrict file operations for privileged users.

MitigationReview and remediate the permission configuration in ZTE OTCP to enforce proper authorization controls on file operations. Apply any vendor-supplied patches or security updates addressing this access control weakness.

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
Otcp FirmwareOperating system
Affected:< 2.21.40.06

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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 ZTE OTCP firmware version
    Locate the firmware version information in the ZTE OTCP system - this is typically found in the system information page, CLI show version command, or system settings panel
    Affected if The installed firmware version is lower than 2.21.40.06
  2. Verify if file operation features are accessible
    Check whether the file management or file operation interface is exposed to authenticated users - this includes any web panel, CLI file commands, or API endpoints that allow file deletion or modification
    Affected if High-privilege authenticated users can access file operation features without additional authorization checks
  3. Inspect permission configuration for file operations
    Review the authorization or permission settings that control which users can perform file delete and modify actions within ZTE OTCP - look for role-based access control (RBAC) settings or file operation permission policies
    Affected if The permission configuration allows privileged users to perform unrestricted file operations without proper authorization validation
  4. Confirm authenticated access is possible
    Determine if the system allows authenticated access for privileged accounts - verify that user authentication is enabled and high-privilege user accounts exist in the ZTE OTCP environment
    Affected if Authenticated attackers with high privileges can access the system

You are affected if your ZTE OTCP firmware version is below 2.21.40.06 AND your system allows authenticated high-privilege users to perform file delete/modify operations without proper authorization controls.

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.21.40.06 or later
Fixed in 2.21.40.06
Interim mitigation

Review and remediate the permission configuration in ZTE OTCP to enforce proper authorization controls on file operations. Apply any vendor-supplied patches or security updates addressing this access control weakness.

Recommended fix Moderate confidence

ZTE OTCP Firmware version 2.21.40.06 or later

  1. 1. Identify the current firmware version of the ZTE OTCP device by accessing the device management interface or using the appropriate CLI command.
  2. 2. Navigate to the official ZTE support portal at support.zte.com.cn and locate the firmware download section for the OTCP product.
  3. 3. Download the latest OTCP firmware version (2.21.40.06 or higher) from the official ZTE support site.
  4. 4. Review the firmware upgrade instructions provided by ZTE in the product documentation or release notes.
  5. 5. Apply the firmware upgrade to the OTCP device following the recommended upgrade procedure, ensuring stable power supply during the process.
  6. 6. After upgrade completion, verify the new firmware version is installed correctly.
  7. 7. Confirm the vulnerability is remediated by verifying proper permission settings are in place according to ZTE's security configuration guidelines.
Caveat Firmware upgrades may require device downtime and should be tested in a non-production environment first; review ZTE release notes for any configuration changes or migration requirements

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

Fix this in Otcp Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23143 — 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-23143 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