LiveActive security incident?Get immediate response
CVE Record

CVE-2025-48633: In hasAccountsOnAnyUser of DevicePolicyManagerService.java, there is a possible way to add a Device Owner a...

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.

MediumCVSS 5.5Known exploitedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-48633 is an Android privilege issue that may let a local app or user add a Device Owner after setup. Device Owner status is highly privileged for enterprise management. The public record rates it medium because exploitation is local and requires low privileges, with no user interaction.

Executive priority

Treat as a medium-priority mobile fleet issue. It is not cited as actively exploited, but Device Owner abuse can undermine enterprise control. Prioritize patch tracking for managed Android devices and high-risk users.

Technical view

The flaw is a logic error in DevicePolicyManagerService.java, in hasAccountsOnAnyUser. It can permit adding a Device Owner after provisioning. CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, no user interaction, high confidentiality impact, no integrity or availability impact listed.

Likely exposure

Android 13, 14, 15, and 16 are listed as affected. Exposure is most relevant to managed Android fleets, BYOD environments, and devices allowing untrusted local apps. Other Android versions are listed as unaffected by default in the provided record.

Exploitation context

The sources say exploitation is local, requires low privileges, and needs no user interaction. CISA KEV status is false in the provided data, so there is no cited evidence of known active exploitation here.

Researcher notes

Public details identify the vulnerable Android framework area and patch reference, but not a complete exploit narrative. Avoid assuming remote exploitation or active abuse. Review the linked AOSP change and Android bulletin for code-level remediation context.

Mitigation direction

  • Apply Android security updates that include the December 2025 bulletin fixes.
  • Prioritize managed Android devices and devices used for sensitive corporate access.
  • Check OEM and carrier update guidance for exact patched builds.
  • Restrict installation of untrusted apps where enterprise policy allows.

Validation and detection

  • Inventory Android 13 through 16 devices in scope.
  • Verify each device security patch level against vendor guidance.
  • Confirm MDM records for unexpected or unauthorized Device Owner enrollment.
  • Review Android security bulletin and OEM advisories for patched build details.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-48633 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2025-48633Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid16, 15, 14, 13unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.