# CVE-2018-9070: Security feature bypass in Lenovo Smart Assistant

> Physical attackers can bypass security controls to enter factory test mode, enabling unauthorized code execution and privilege escalation on Lenovo Smart Assistant devices.

- **Severity:** Medium 6.4 (`CVSS:3.0/AV:P/AC:H/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:** 13 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-44ph-gjhm-wmq8

## What is CVE-2018-9070?

CVE-2018-9070 is a medium-severity vulnerability in Lenovo Smart Assistant, published on 13 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

For the Lenovo Smart Assistant Android app versions earlier than 12.1.82, an attacker with physical access to the smart speaker can, by pressing a specific button sequence, enter factory test mode and enable a web service intended for testing the device. As with most test modes, this provides extra privileges, including changing settings and running code. Lenovo Smart Assistant is an Amazon Alexa-enabled smart speaker developed by Lenovo.

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

It affects 1 product.


Products: Lenovo Smart Assistant.

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

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

## Is CVE-2018-9070 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-9070 is a medium-severity vulnerability in Lenovo Smart Assistant, published on 13 Jul 2018. 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-9070 in the wild and no public exploit code.

Affected product: Lenovo Smart Assistant. 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-9070/ (Markdown: https://insights.sbomify.com/CVE-2018-9070/index.md)
```

## Sources

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

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