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

> Remote attackers can eavesdrop on robot-user calls by guessing a hardcoded six-digit credential in temi Robox OS and Android app.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-95v9-45f9-x3wp

## What is CVE-2020-16170?

CVE-2020-16170 is a high-severity vulnerability in n/a, published on 11 Aug 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 temi Robox OS prior to 120, temi Android app up to 1.3.7931 allows remote attackers to listen in on any ongoing calls between temi robots and their users if they can brute-force/guess a six-digit value via unspecified vectors.

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

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

It affects 1 product.


Products: Robotemi Temi.

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

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

## Is CVE-2020-16170 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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