In hasAccountsOnAnyUser of DevicePolicyManagerService.java, there is a possible way to add a Device Owner after provisioning due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
History

Tue, 09 Dec 2025 03:15:00 +0000

Type Values Removed Values Added
References
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'active', 'Technical Impact': 'total'}, 'version': '2.0.3'}

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}


Mon, 08 Dec 2025 19:45:00 +0000

Type Values Removed Values Added
First Time appeared Google
Google android
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:o:google:android:13.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:14.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:15.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:*:*:*:*:*:*:*
Vendors & Products Google
Google android
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Mon, 08 Dec 2025 17:15:00 +0000

Type Values Removed Values Added
Description In hasAccountsOnAnyUser of DevicePolicyManagerService.java, there is a possible way to add a Device Owner after provisioning due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
References
Metrics kev

{'dateAdded': '2025-12-02T00:00:00+00:00', 'dueDate': '2025-12-23T00:00:00+00:00'}


cve-icon MITRE

Status: PUBLISHED

Assigner: google_android

Published: 2025-12-08T16:57:49.260Z

Updated: 2025-12-09T04:55:50.979Z

Reserved: 2025-05-22T18:12:39.228Z

Link: CVE-2025-48633

cve-icon Vulnrichment

Updated: 2025-12-08T17:59:38.691Z

cve-icon NVD

Status : Analyzed

Published: 2025-12-08T17:16:19.610

Modified: 2025-12-09T18:44:57.533

Link: CVE-2025-48633

cve-icon Redhat

No data.