CVE-2022-20488
High · 7.8CVSS
7.8
EPSS
0.1%
Published
Dec 13, 2022
CISA due date
—
Cloudanix analysis
A bug in Android notifications can let apps on a phone or tablet quietly gain more access than they are supposed to have.
- Exploitation
- Local Privilege
- Attacker needs
- Low Privilege
- Complexity
- Low
- Impact
- Privilege Gain
- Component
- Application
- Class
- Privilege Escalation
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Resource exhaustion in NotificationChannel.java prevents proper persistence of permission settings, allowing a local process to retain elevated privileges beyond intended boundaries.
Why it matters to the business
On affected Android devices, malicious or compromised apps could silently obtain broader device access, increasing risk of data theft, surveillance, or unauthorized actions without user interaction; high ecosystem prevalence amplifies exposure across consumer and enterprise fleets.
How an attack unfolds
An attacker installs or controls an app on the device that triggers repeated notification channel operations to exhaust resources, causing permission settings to fail to persist and thereby granting the app unintended elevated privileges.
How to fix it
Update affected Android devices to the latest vendor-provided security patch that resolves the resource handling issue in NotificationChannel; apply monthly security updates promptly and verify device patch level after installation.
How to confirm the fix worked
Confirm devices report a patch level after the December 2022 security bulletin or later; test notification permission behavior under resource-constrained conditions on updated builds to ensure settings persist correctly.
Typical attack path
- App is installed or already present on the device
- App repeatedly creates or modifies notification channels to trigger resource exhaustion
- Permission persistence fails due to the exhaustion condition
- App retains or escalates to higher privileges without additional user action
- Attacker abuses the elevated privileges for further actions on the device
How to detect it
Review system logs for repeated notification channel creation failures or resource exhaustion events around permission changes; correlate with app installation or execution timelines on devices that remain on vulnerable builds.
What your security team should do
- Prioritize patching all managed Android devices to the latest security update
- Enforce automatic updates and monitor enterprise device compliance dashboards
- Review app permission policies and restrict sideloading where possible
- Include notification-related resource usage in mobile threat detection rules
The record
In NotificationChannel of NotificationChannel.java, there is a possible failure to persist permissions settings due to resource exhaustion. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12L Android-13Android ID: A-242703217
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Android | platform/frameworks/base | 10:0 | 10:2022-12-01 |
| Android | platform/frameworks/base | 11:0 | 11:2022-12-01 |
| Android | platform/frameworks/base | 12:0 | 12:2022-12-01 |
| Android | platform/frameworks/base | 12L:0 | 12L:2022-12-01 |
| Android | platform/frameworks/base | 13:0 | 13:2022-12-01 |
| Ubuntu:16.04:LTS | android-platform-frameworks-base | 0 | No fix |
| Ubuntu:18.04:LTS | android-platform-frameworks-base | 0 | No fix |
| Ubuntu:20.04:LTS | android-platform-frameworks-base | 0 | No fix |
| Ubuntu:22.04:LTS | android-platform-frameworks-base | 0 | No fix |
| Ubuntu:24.04:LTS | android-platform-frameworks-base | 0 | No fix |
| Ubuntu:24.10 | android-platform-frameworks-base | 0 | No fix |
| Ubuntu:Pro:16.04:LTS | android-platform-frameworks-base | 0 | No fix |
| Ubuntu:Pro:18.04:LTS | android-platform-frameworks-base | 0 | No fix |
| Ubuntu:Pro:20.04:LTS | android-platform-frameworks-base | 0 | No fix |
Related vulnerabilities
- CVE-2025-48631 In onHeaderDecoded of LocalImageResolver.java, there is a possible persistent denial of… Also affects platform/frameworks/base
- CVE-2024-32896 there is a possible way to bypass due to a logic error in the code. Also affects platform/frameworks/base
- CVE-2024-0053 In getCustomPrinterIcon of PrintManagerService.java, there is a possible way to view… Also affects platform/frameworks/base
- CVE-2024-0048 In Session of AccountManagerService.java, there is a possible method to retain foreground… Also affects platform/frameworks/base
- CVE-2024-0046 In installExistingPackageAsUser of InstallPackageHelper.java, there is a possible carrier… Also affects platform/frameworks/base
- CVE-2023-40094 In keyguardGoingAway of ActivityTaskManagerService.java, there is a possible lock screen… Also affects platform/frameworks/base
- CVE-2023-40074 In saveToXml of PersistableBundle.java, invalid data could lead to local persistent… Also affects platform/frameworks/base
- CVE-2023-35668 In visitUris of Notification.java, there is a possible way to display images from another… Also affects platform/frameworks/base