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

> Hard-coded SSH keys allow attackers to remotely log in as root on Amino Communications devices, leading to full system compromise.

- **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-xf35-pm29-wrq6

## What is CVE-2020-10210?

CVE-2020-10210 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

Because of hard-coded SSH keys for the root user in Amino Communications AK45x series, AK5xx series, AK65x series, Aria6xx series, Aria7/AK7Xx series, Kami7B, an attacker may remotely log in through SSH.

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

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

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-10210?

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

## Is CVE-2020-10210 being exploited?

There is no known exploitation of CVE-2020-10210 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-10207](https://insights.sbomify.com/CVE-2020-10207/): 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-10210 and fix it if it is affected.

What it is: CVE-2020-10210 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-10210 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-10210/ (Markdown: https://insights.sbomify.com/CVE-2020-10210/index.md)
```

## Sources

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

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