# CVE-2020-24217: Missing authorization in n/a

> Unauthenticated attackers can upload custom firmware components to HiSilicon-based IPTV encoders, potentially achieving arbitrary code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 6 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vwf4-cwv7-v664

## What is CVE-2020-24217?

CVE-2020-24217 is a critical missing authorization vulnerability in n/a, published on 6 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the box application on HiSilicon based IPTV/H.264/H.265 video encoders. The file-upload endpoint does not enforce authentication. Attackers can send an unauthenticated HTTP request to upload a custom firmware component, possibly in conjunction with command injection, to achieve arbitrary code execution.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 7 products.


Products: Jtechdigital H.264 Iptv Encoder 1080p\@60hz Firmware, Provideoinstruments Vecaster-4k-Hevc Firmware, Provideoinstruments Vecaster-Hd-H264 Firmware, Provideoinstruments Vecaster-Hd-Hevc Firmware, Provideoinstruments Vecaster-Hd-Sdi Firmware, Szuray Iptv\/H.264 Video Encoder Firmware, Szuray Iptv\/H.265 Video Encoder Firmware.

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

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

## Is CVE-2020-24217 being exploited?

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

Public exploit code:

- HiSilicon Video Encoders - RCE via unauthenticated command injection (exploitdb)
- HiSilicon video encoders - RCE via unauthenticated upload of malicious firmware (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-24214](https://insights.sbomify.com/CVE-2020-24214/): Denial of service in n/a (critical 9.8)
- [CVE-2020-24215](https://insights.sbomify.com/CVE-2020-24215/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-24216](https://insights.sbomify.com/CVE-2020-24216/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-24217 is a critical missing authorization vulnerability in n/a, published on 6 Oct 2020. 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-24217 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-24217/ (Markdown: https://insights.sbomify.com/CVE-2020-24217/index.md)
```

## Sources

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

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