# CVE-2020-16169: Auth bypass in n/a

> Remote attackers can bypass authentication to gain elevated privileges and control audio, video, and motors on temi robots.

- **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:** 7 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f84c-pj2g-x4f3

## What is CVE-2020-16169?

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

### Official description

Authentication Bypass Using an Alternate Path or Channel in temi Robox OS prior to120, temi Android app up to 1.3.7931 allows remote attackers to gain elevated privileges on the temi and have it automatically answer the attacker's calls, granting audio, video, and motor control via unspecified vectors.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Robotemi Robox Os.

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

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

## Is CVE-2020-16169 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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