# CVE-2018-20007: Missing authorization in n/a

> Physical attackers can access the UART interface to gain root privileges and exfiltrate sensitive data from Yeelight Smart AI Speakers.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3pw5-pqx4-4928

## What is CVE-2018-20007?

CVE-2018-20007 is a medium-severity missing authorization vulnerability in n/a, published on 16 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Yeelight Smart AI Speaker 3.3.10_0074 devices have improper access control over the UART interface, allowing physical attackers to obtain a root shell. The attacker can then exfiltrate the audio data, read cleartext Wi-Fi credentials in a log file, or access other sensitive device and user information.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2018-20007?

It affects 1 product.


Products: Yeelight Smart Ai Speaker Firmware.

## How do I fix CVE-2018-20007?

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

## Is CVE-2018-20007 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20007 and fix it if it is affected.

What it is: CVE-2018-20007 is a medium-severity missing authorization vulnerability in n/a, published on 16 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20007 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-2018-20007/ (Markdown: https://insights.sbomify.com/CVE-2018-20007/index.md)
```

## Sources

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

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