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

> Remote attackers can access the REST API and MQTT broker to send custom data or requests due to origin validation errors.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xwx9-xrv6-2fwc

## What is CVE-2020-16168?

CVE-2020-16168 is a medium-severity missing authorization vulnerability in n/a, published on 7 Aug 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Origin Validation Error in temi Robox OS prior to 120, temi Android app up to 1.3.7931 allows remote attackers to access the REST API and MQTT broker used by the temi and send it custom data/requests via unspecified vectors.

Weakness: CWE-346 (Origin Validation Error)

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

It affects 1 product.


Products: Robotemi Temi Firmware.

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

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

## Is CVE-2020-16168 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-16168 is a medium-severity missing authorization vulnerability in n/a, published on 7 Aug 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-16168 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-16168/ (Markdown: https://insights.sbomify.com/CVE-2020-16168/index.md)
```

## Sources

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

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