# CVE-2020-28715: Other in n/a

> Attackers can execute arbitrary code, escalate privileges, and cause denial of service in the LeTV X43 kdmserver service.

- **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:** 21 Aug 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-28wf-jx5m-6fhg

## What is CVE-2020-28715?

CVE-2020-28715 is a critical vulnerability in n/a, published on 21 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in kdmserver service in LeEco LeTV X43 version V2401RCN02C080080B04121S, allows attackers to execute arbitrary code, escalate privileges, and cause a denial of service (DoS).

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

It affects 1 product.


Products: Leeco Letv X43 Firmware.

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

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

## Is CVE-2020-28715 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28715 is a critical vulnerability in n/a, published on 21 Aug 2023. 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-28715 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-28715/ (Markdown: https://insights.sbomify.com/CVE-2020-28715/index.md)
```

## Sources

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

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