Cloudanix VulnDB

CVE-2022-20448

Medium · 5.5

CVSS

5.5

EPSS

0.1%

Published

Nov 8, 2022

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A bug in Android lets one person on a shared phone or tablet secretly read notification messages meant for someone else.

Exploitation
Local Privilege
Attacker needs
Low Privilege
Complexity
Low
Impact
Privilege Gain
Component
Application
Class
Authorization Bypass
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Permissions bypass in NotificationManagerService.java allows an app running as one user to access notification data belonging to another user on the same device, resulting in unauthorized cross-user data exposure and local privilege escalation.

Why it matters to the business

On multi-user Android devices, an attacker with a low-privileged local account can read sensitive notification data from other users without additional privileges or user interaction, increasing risk of data leakage on shared or managed devices.

How an attack unfolds

An attacker with local access on an affected Android device invokes the buzzBeepBlinkLocked method through a malicious application or process; the missing permission check permits reading notification state and content belonging to other users on the device.

How to fix it

Apply the security patch released in the November 2022 Android Security Bulletin for Android versions 10 through 13; upgrade devices to the fixed builds that address A-237540408.

How to confirm the fix worked

Verify that devices are running a build containing the November 2022 security patch level or later; confirm the vulnerable code path in NotificationManagerService.java is no longer reachable without proper permissions.

Typical attack path

  1. Obtain a local shell or install a malicious app on the target Android device
  2. Trigger NotificationManagerService.buzzBeepBlinkLocked without the required cross-user permission
  3. Read notification data belonging to other users
  4. Escalate to higher privileges or exfiltrate exposed information

How to detect it

Review system logs for NotificationManagerService calls originating from one user context that reference data of another user; look for unusual cross-user notification queries in logcat or audit logs around the time of suspected access.

What your security team should do

  • Prioritize deployment of Android security updates to all managed devices within 30 days
  • Enforce device encryption and strong user separation policies on multi-user deployments
  • Monitor Android security bulletin releases for backported fixes on older branches

The record

In buzzBeepBlinkLocked of NotificationManagerService.java, there is a possible way to share data across users due to a permissions bypass. 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-237540408

Affected packages

Ecosystem Package Introduced Fixed
Android platform/frameworks/base 10:0 10:2022-11-01
Android platform/frameworks/base 11:0 11:2022-11-01
Android platform/frameworks/base 12:0 12:2022-11-01
Android platform/frameworks/base 12L:0 12L:2022-11-01
Android platform/frameworks/base 13:0 13:2022-11-01
Ubuntu:18.04:LTS android-framework-23 0 No fix
Ubuntu:20.04:LTS android-framework-23 0 No fix
Ubuntu:22.04:LTS android-framework-23 0 No fix
Ubuntu:24.04:LTS android-framework-23 0 No fix
Ubuntu:24.10 android-framework-23 0 No fix
Ubuntu:Pro:18.04:LTS android-framework-23 0 No fix
Ubuntu:Pro:20.04:LTS android-framework-23 0 No fix

Related vulnerabilities