# CVE-2020-16167: Missing authorization in n/a

> Remote attackers can intercept and answer calls intended for other users, gaining motor control and audio/video access to the robot.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 7 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qp4w-65rx-2h9g

## What is CVE-2020-16167?

CVE-2020-16167 is a critical missing authorization 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

Missing Authentication for Critical Function in temi Robox OS prior to 120, temi Android app up to 1.3.7931 allows remote attackers to receive and answer calls intended for another temi user. Answering the call this way grants motor control of the temi in addition to audio/video via unspecified vectors.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Robotemi Launcher Os.

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

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

## Is CVE-2020-16167 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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