# CVE-2020-10207: Hardcoded credentials in n/a

> Remote attackers can use hard-coded credentials in EntoneWebEngine to retrieve and modify device settings on Amino set-top boxes.

- **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:** 29 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-44rv-rqpv-5h55

## What is CVE-2020-10207?

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

### Official description

Use of Hard-coded Credentials in EntoneWebEngine in Amino Communications AK45x series, AK5xx series, AK65x series, Aria6xx series, Aria7/AK7Xx series and Kami7B allows remote attackers to retrieve and modify the device settings.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 6 products.


Products: Amino Ak45x Firmware, Amino Ak5xx Firmware, Amino Ak65x Firmware, Amino Aria6xx Firmware, Amino Aria7xx Firmware, Amino Kami7b Firmware.

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

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

## Is CVE-2020-10207 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-10208](https://insights.sbomify.com/CVE-2020-10208/): Command injection in n/a (critical 9.9)
- [CVE-2020-10210](https://insights.sbomify.com/CVE-2020-10210/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-10209](https://insights.sbomify.com/CVE-2020-10209/): Command injection in n/a (high 8.1)
- [CVE-2020-10206](https://insights.sbomify.com/CVE-2020-10206/): Hardcoded credentials in n/a (medium 4.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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