# CVE-2021-21737: Missing authorization in ZXV10 B860H V5.0

> Attackers can tamper with the system desktop and customization functions on ZTE Smart STBs due to insufficient access control protections.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-c6fv-7r7c-32q7

## What is CVE-2021-21737?

CVE-2021-21737 is a high-severity missing authorization vulnerability in ZXV10 B860H V5.0, published on 24 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A smart STB product of ZTE is impacted by a permission and access control vulnerability. Due to insufficient protection of system application, attackers could use this vulnerability to tamper with the system desktop and affect system customization functions. This affects: ZXV10 B860H V5.0, V83011303.0010, V83011303.0016

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2021-21737?

It affects 1 product.


Products: Zte Zxv10 B860h V5.0 Firmware.

## How do I fix CVE-2021-21737?

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

## Is CVE-2021-21737 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-21737 and fix it if it is affected.

What it is: CVE-2021-21737 is a high-severity missing authorization vulnerability in ZXV10 B860H V5.0, published on 24 Jun 2021. 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-2021-21737 in the wild and no public exploit code.

Affected product: ZXV10 B860H V5.0. 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-2021-21737/ (Markdown: https://insights.sbomify.com/CVE-2021-21737/index.md)
```

## Sources

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

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