CVE-2022-23144
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 · uneditedThere is a broken access control vulnerability in ZTE ZXvSTB product. Due to improper permission control, attackers could use this vulnerability to delete the default application type, which affects normal use of system.
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 confidenceBroken access control vulnerability in ZTE ZXvSTB set-top box devices allows unauthenticated or low-privileged attackers to delete the default application type due to improper permission control, causing system disruption. The CVSS 9.1 indicates exploitation likely requires no authentication and has complete impact on system availability.
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<= 2.01.02.01<= 2.01.02.01<= 2.01.02.01<= 2.01.02.01<= 2.01.02.01<= 2.01.02.01<= 2.01.02.01<= 2.01.02.01CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the ZTE set-top box modelAccess the device web interface (typically at http://192.168.1.1 or similar) and look for the model number in the status or device information page. Alternatively, use network scanning tools to probe the device and examine HTTP responses for model identifiers in headers or HTML.Affected if The model number matches one of the affected models: B76hv3, B766v2, B800v2, B860av2.1, B860h, B866v2 H, B866v5 W10, or B960gv1
-
Check the installed firmware versionIn the device web interface, navigate to the maintenance, system, or settings section to find the firmware version information. If telnet or SSH access is available, log in and run commands such as 'version', 'show version', or check /proc/version if accessible.Affected if The firmware version is 2.01.02.01 or lower (any version up to and including 2.01.02.01)
-
Verify if the device management interface is exposed to unauthenticated accessAttempt to access the device administrative web interface from an untrusted network segment without providing credentials. Check if authentication is enforced or if unauthenticated requests are accepted. Also probe for common administrative endpoints such as /web or /admin.Affected if The administrative interface or management functions are accessible without requiring authentication from the network segment being tested
-
Check for the vulnerable application deletion endpointIf the web interface is accessible, examine the available API endpoints or functionality related to application management. Look for endpoints that handle application type deletion or modification. Test if low-privileged or unauthenticated users can access these functions.Affected if The application management or deletion functionality can be accessed without proper authorization or by low-privileged users
A user is affected if the device is one of the listed ZTE ZXA10 models running firmware version 2.01.02.01 or lower AND the management interface is accessible without authentication, allowing unauthorized deletion of the default application type.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor-supplied firmware patches when available; until then, isolate affected devices on restricted network segments and implement additional authentication layers to mitigate unauthorized access to administrative functions.
- Consultation6.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,520.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23144 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23144 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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