# CVE-2020-21406: Denial of service in n/a

> Attackers can cause a denial of service on RK Smart TV Box MAX and V88 devices via the switchNextDisplayInterface service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 20 Jul 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vjp2-9hqr-v334

## What is CVE-2020-21406?

CVE-2020-21406 is a high-severity denial of service vulnerability in n/a, published on 20 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in RK Smart TV Box MAX and V88 SmartTV box that allows attackers to cause a denial of service via the switchNextDisplayInterface service.

## Which versions are affected by CVE-2020-21406?

It affects 2 products.


Products: Rk Max Smart Tv Box Project Rk Max Smart Tv Box Firmware, V88 Smart Tv Box Project V88 Smart Tv Box Firmware.

## How do I fix CVE-2020-21406?

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

## Is CVE-2020-21406 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-21406 and fix it if it is affected.

What it is: CVE-2020-21406 is a high-severity denial of service vulnerability in n/a, published on 20 Jul 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-2020-21406 in the wild and no public exploit code.

Affected product: n/a. 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-2020-21406/ (Markdown: https://insights.sbomify.com/CVE-2020-21406/index.md)
```

## Sources

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

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