# CVE-2019-1010221: Privilege escalation in LineageOS

> An attacker with physical access and enabled ADB can escalate privileges to root by setting a specific system property, affecting LineageOS users.

- **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:** 23 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qj8f-q4w4-3qfp

## What is CVE-2019-1010221?

CVE-2019-1010221 is a medium-severity vulnerability in LineageOS, published on 23 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

LineageOS 16.0 and earlier is affected by: Incorrect Access Control. The impact is: The property checked by `adb root` can also be set in a normal adb shell session. The component is: adb shell (patches to fix this are at https://review.lineageos.org/c/LineageOS/android_system_core/+/234800, https://review.lineageos.org/c/LineageOS/android_device_lineage_sepolicy/+/234799). The attack vector is: When adb is enabled, and an attacker has physical access, `adb shell setprop service.adb.root 1` allows restarting adb as root.

## Which versions are affected by CVE-2019-1010221?

It affects 1 product.


Products: Lineageos Lineageos.

## How do I fix CVE-2019-1010221?

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

## Is CVE-2019-1010221 being exploited?

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

## Other vulnerabilities in LineageOS

- [CVE-2017-6899](https://insights.sbomify.com/CVE-2017-6899/): Null dereference in n/a (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1010221 and fix it if it is affected.

What it is: CVE-2019-1010221 is a medium-severity vulnerability in LineageOS, published on 23 Jul 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-2019-1010221 in the wild and no public exploit code.

Affected product: LineageOS. 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-2019-1010221/ (Markdown: https://insights.sbomify.com/CVE-2019-1010221/index.md)
```

## Sources

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

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