Device Policy / MDM Capability Abuse

← Privileged System-Provider Activation

device_policy_mdm_capability_abuse   HARD

Description

A Device Admin / DevicePolicyManager receiver acts as a device-wide policy authority but validates policy parameters or caller/state insufficiently, so app-controlled policy changes, work-profile boundary confusion, or policy-state desync escalate privilege or cause DoS across the device. The DPC’s authority - not just ‘DeviceAdmin used’ - is the boundary (Android DevicePolicyManagerService logic-flaw CVE-2025-48553 class).

How it works

A Device Admin / DevicePolicyManager receiver is a device-wide policy authority: it can wipe data, disable the camera, or weaken the password policy. Here policy changes are applied without verifying the caller is the currently-registered active admin and without validating parameters, so an untrusted caller triggers a full device wipe (and could push a weak password-quality value), a privilege escalation across the work-profile / policy boundary (Android DevicePolicyManagerService logic-flaw CVE-2025-48553 class). The secure path verifies the caller is the active admin and validates the parameter before applying, denying untrusted or invalid requests. On device the “real state” panel shows this app’s actual DevicePolicyManager posture. To fully arm the capability, register a DeviceAdminReceiver and activate it via ACTION_ADD_DEVICE_ADMIN (or provision DVMA as device owner via adb dpm set-device-owner).

How to exercise it. DVMA is the harness - open this module from the home index and tap the demo action. The screen ships the malicious input and simulates the attacker (e.g. the companion app, crafted intent, or scanned payload) in-process, and the evidence panel prints the proof. The Tools (optional) and Attack inputs below are only needed to reproduce the exploit end-to-end on a real device.

Exploit steps

1. Set up. Build DVMA with a flavor that enables the Privileged System-Provider Activation category (e.g. --dart-define-from-file=config/flavors/dev.json) and run on an Android emulator you control. The demo needs no external tooling; for the optional on-device reproduction the relevant tools are: adb, drozer, jadx.
2. Locate the target. From the home index, open Device Policy / MDM Capability Abuse (device_policy_mdm_capability_abuse). The How it works section above describes this module’s specific weakness; the screen states the intended-secure behavior and exposes the vulnerable action.
3. Exploit. Drive the provider-activation / enablement workflow (accessibility, notification-listener, VPN, IME, phone-account, MediaProjection, credential-provider) and confirm the granted capability is invoked on an untrusted caller’s behalf - the enablement flow is the boundary.
4. Observe the evidence. Trigger the vulnerable action and read the evidence panel - it prints the concrete proof (leaked value, accepted replay, executed payload, or unauthorized result).
5. Contrast with the secure path. Run the module’s secure/hardened action (where provided) and confirm the same attack is rejected - this is what a correct implementation should do.

Tools (optional)

• adb
• drozer
• jadx

Attack inputs

Payloads/artifacts you author for the on-device attack. The demo already ships and simulates these in-process (e.g. the malicious companion app / crafted intent is emulated inside the screen), so you only need to craft them to reproduce the exploit on a real device:

• malicious companion app
• crafted policy payload

Real-world references

Concrete public disclosures that match this vulnerability class:

• CVE-2025-48553 (Android DevicePolicyManagerService logic flaw)