dbcve.org
Zxv10 Et301 FirmwareOperating system · Zte

CVE-2024-22069

HIGH · 8.8 CVSS v3.1 Published 2024-08-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
There is a permission and access control vulnerability of ZTE's ZXV10 XT802/ET301 product.Attackers with common permissions can log in the terminal web and change the password of the administrator illegally by intercepting requests to change the passwords.

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

This is an improper access control vulnerability in ZTE ZXV10 XT802/ET301 firmware where low-privileged users with 'common permissions' can intercept password change requests and illegally reset the administrator password, achieving privilege escalation. The web application fails to properly authorize password change operations, allowing horizontal privilege escalation.

MitigationApply the vendor firmware update from ZTE that addresses this access control flaw. Until patched, monitor for unauthorized administrative account changes and restrict web interface access to trusted personnel only.

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
Zxv10 Et301 FirmwareOperating system
Affected:< v3.22.11p3
Zxv10 Xt802 FirmwareOperating system
Affected:< v2.24.10p1

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

CVSS:3.1/AV:N/AC:L/PR:L/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
    Locate the device label or access the web management interface to confirm the model is ZTE ZXV10 XT802 or ZTE ZXV10 ET301
    Affected if The device model is either ZTE ZXV10 XT802 or ZTE ZXV10 ET301
  2. Determine the firmware version
    Access the web management interface and navigate to the system status or firmware information page to view the installed firmware version
    Affected if The firmware version is below v3.22.11p3 for ET301 or below v2.24.10p1 for XT802
  3. Verify web management interface accessibility
    Confirm the device web management interface (HTTP/HTTPS on the LAN or WAN interface) is reachable from your network
    Affected if The web interface is accessible and the device has one of the affected firmware versions listed above
  4. Review user account privileges
    Check the user account configuration in the web management interface to identify if standard or common permission-level accounts exist alongside administrator accounts
    Affected if Standard user accounts exist and the firmware version is in the affected range, indicating the privilege escalation could be exploited

The environment is affected if the device is a ZTE ZXV10 XT802 or ET301 running firmware below v3.22.11p3 or v2.24.10p1 respectively, and the web management interface is accessible with standard user accounts present.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor firmware update from ZTE that addresses this access control flaw. Until patched, monitor for unauthorized administrative account changes and restrict web interface access to trusted personnel only.

Recommended fix High confidence

ZXV10 ET301 v3.22.11p3 or later; ZXV10 XT802 v2.24.10p1 or later

  1. 1. Identify the exact ZTE device model (ET301 or XT802) in your environment
  2. 2. Download the firmware from the official ZTE support portal (support.zte.com.cn) - ensure you get the specific version for your model
  3. 3. For ET301: upgrade to firmware version v3.22.11p3 or later
  4. 4. For XT802: upgrade to firmware version v2.24.10p1 or later
  5. 5. Access the device's web management interface using admin credentials
  6. 6. Navigate to the firmware upgrade or system update section in the administrative panel
  7. 7. Upload the downloaded firmware file and initiate the upgrade process
  8. 8. Wait for the device to complete the firmware update and reboot automatically if required

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

Fix this in Zxv10 Et301 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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