# CVE-2022-23144: Missing authorization in ZXvSTB

> Attackers can delete default application types in ZTE ZXvSTB devices due to broken access control, disrupting normal system usage.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2022
- **Updated:** 22 May 2025
- **Also known as:** GHSA-4xjp-gp7m-jj8v

## What is CVE-2022-23144?

CVE-2022-23144 is a critical missing authorization vulnerability in ZXvSTB, published on 23 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There 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.

## Which versions are affected by CVE-2022-23144?

It affects 15 products.


Products: Zte Zxa10 B700v7 Firmware, Zte Zxa10 B710c-A12 Firmware, Zte Zxa10 B710s2-A19 Firmware, Zte Zxa10 B766v2 Firmware, Zte Zxa10 B76hv3 Firmware, Zte Zxa10 B800v2 Firmware, Zte Zxa10 B836ct-A15 Firmware, Zte Zxa10 B860av2.1 Firmware, Zte Zxa10 B860h Firmware, Zte Zxa10 B866v2-H Firmware, Zte Zxa10 B866v5-W10 Firmware, Zte Zxa10 B960gv1 Firmware, Zte Zxa10 S100v Firmware, Zte Zxa10 S200a Firmware, Zte Zxa10 S200t Firmware.

## How do I fix CVE-2022-23144?

No fix has been published for CVE-2022-23144 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-23144 being exploited?

There is no known exploitation of CVE-2022-23144 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23144 and fix it if it is affected.

What it is: CVE-2022-23144 is a critical missing authorization vulnerability in ZXvSTB, published on 23 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23144 in the wild and no public exploit code.

Affected product: ZXvSTB. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-23144/ (Markdown: https://insights.sbomify.com/CVE-2022-23144/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-23144
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-23144
- OSV: https://osv.dev/vulnerability/CVE-2022-23144

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-23144/
Summaries are generated and may contain mistakes; the official description above is the record.