dbcve.org
Zxr10 1800 2s FirmwareOperating system · Zte

CVE-2024-22068

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-10
Fix available
A fix is available. Upgrade to 6.00.10 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
Improper Privilege Management vulnerability in ZTE ZXR10 1800-2S series ,ZXR10 2800-4,ZXR10 3800-8,ZXR10 160 series on 64 bit allows Functionality Bypass.This issue affects ZXR10 1800-2S series ,ZXR10 2800-4,ZXR10 3800-8,ZXR10 160 series: V4.00.10 and earlier.

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 · high confidence

Improper Privilege Management vulnerability in ZTE ZXR10 router series (1800-2S, 2800-4, 3800-8, 160) on 64-bit firmware allows authenticated users to bypass intended security restrictions due to improper privilege enforcement. This medium-severity (CVSS 6.5) issue affects versions V4.00.10 and earlier.

MitigationApply vendor-supplied firmware update from ZTE to patch the improper privilege management vulnerability; if no update available, restrict administrative access to trusted personnel and monitor for unauthorized functionality access.

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
Zxr10 1800 2s FirmwareOperating system
Affected:< 6.00.10
Zxr10 2800 4 FirmwareOperating system
Affected:< 6.00.10
Zxr10 3800 8 FirmwareOperating system
Affected:< 6.00.10
Zxr10 160 FirmwareOperating system
Affected:< 6.00.10

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

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

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 ZXR10 router model
    Access the router admin interface or CLI and determine the exact model number (1800-2S, 2800-4, 3800-8, or 160) from the system information or device label
    Affected if The model is one of: 1800-2S, 2800-4, 3800-8, or 160
  2. Check the installed firmware version
    Access the router web interface or CLI and locate the firmware version information, typically found under System, Device Info, or Version status screens
    Affected if The firmware version is V4.00.10 or earlier, or any version below 6.00.10
  3. Verify firmware architecture
    Check the router firmware details or system information to confirm if it is 64-bit firmware
    Affected if The device is running 64-bit firmware on an affected model
  4. Confirm user authentication is enabled
    Verify that user authentication is configured on the router, typically under User Management, Admin settings, or AAA configuration
    Affected if User authentication is enabled and the device has multiple user accounts with different privilege levels
  5. Review privilege assignment configuration
    Examine the router's privilege or role configuration settings to see if lower-privilege authenticated users can access higher-privilege functions or commands
    Affected if Authenticated users with standard or limited privileges can access administrative or elevated functions they should not be permitted to use

The environment is affected if the ZXR10 model is a 1800-2S, 2800-4, 3800-8, or 160 running 64-bit firmware version below 6.00.10 with authenticated user access configured.

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 6.00.10 or later
Fixed in 6.00.10
Interim mitigation

Apply vendor-supplied firmware update from ZTE to patch the improper privilege management vulnerability; if no update available, restrict administrative access to trusted personnel and monitor for unauthorized functionality access.

Recommended fix Moderate confidence

ZTE ZXR10 firmware version 6.00.10 or later for 1800-2S, 2800-4, 3800-8, and 160 series

  1. 1. Navigate to the official ZTE support portal at support.zte.com.cn
  2. 2. Locate the product support page for your specific ZXR10 model (1800-2S, 2800-4, 3800-8, or 160)
  3. 3. Download the firmware version 6.00.10 or later from the downloads section
  4. 4. Access the router's web management interface or CLI
  5. 5. Navigate to the firmware upgrade section (typically under System > Maintenance > Upgrade)
  6. 6. Upload the downloaded firmware file
  7. 7. Wait for the upgrade process to complete - do not power off the device
  8. 8. After reboot, verify the firmware version has been updated to 6.00.10 or later
Caveat Standard firmware upgrade risk - ensure configuration backup before upgrading and verify compatibility with existing network setup

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

Fix this in Zxr10 1800 2s Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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