CVE-2021-39704: App can remain foreground forever without showing any notification and can bypass one time permissions

platform/frameworks/base Updated 02 Oct 2025

Summary

01/03/2022
Yes i
High
Not published

CVE-2021-39704: In deleteNotificationChannelGroup of NotificationManagerService.java, there is a possible way to run foreground service without user notification due to a permissions bypass. Affects platform/frameworks/base across 3 version ranges.

>= 11:0, < 11:2022-03-01 >= 12:0, < 12:2022-03-01 >= 12L:0, < 12L:2022-03-01

Fixed in 11:2022-03-01. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The vulnerability affects the platform/frameworks/base package in the Android ecosystem. This package is a fundamental part of the Android operating system, providing core functionalities and services. It is responsible for managing various system components, including notifications. The vulnerability allows an app to run as a foreground service without displaying any user notification, bypassing one-time permissions. This can lead to a local escalation of privilege without requiring additional execution privileges or user interaction.

Vulnerability Detail

The vulnerability exists in the deleteNotificationChannelGroup method of the NotificationManagerService.java file. It allows an app to exploit a permissions bypass, enabling it to run as a foreground service without notifying the user. This can be abused by malicious apps to gain elevated privileges on the device. The impact of this vulnerability is significant as it can be exploited without user interaction and without the need for additional execution privileges.

How To Fix

Minimum fixed version

11:2022-03-01

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the provided patch or update the affected Android version to mitigate the risk.

Conclusion

The vulnerability in the platform/frameworks/base package allows an app to run as a foreground service without displaying any user notification and bypassing one-time permissions. This can lead to a local escalation of privilege, enabling malicious apps to gain elevated privileges on the device. It is recommended to apply the provided patch or update the affected Android version to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for platform/frameworks/base →

Share this vulnerability

FAQ

The vulnerability allows an app to run as a foreground service without displaying any user notification and bypassing one-time permissions. This can lead to a local escalation of privilege, enabling malicious apps to gain elevated privileges on the device.

No, this vulnerability requires the app to be installed on the device and does not have a remote exploitation vector.

No, user interaction is not needed for exploitation. The app can exploit the vulnerability without any user input.

The vulnerability affects Android versions 10, 11, 12, and 12L. It is recommended to update to a fixed version released after March 1, 2022.

No, there is no known workaround. It is crucial to apply the provided patch or update the affected Android version to mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for platform/frameworks/base.

How To Fix

Minimum fixed version

11:2022-03-01

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback