CVE Vulnerability Catalog

In getAppLabel of ForgetDeviceDialogFragment.java, misleading UI can trick the user into forgetting a device, leading to local escalation of privilege.

In l2c_fcr_clone_buf of l2c_fcr.cc, there is a possible way to trigger controlled heap corruption within the privileged Bluetooth process due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In getApplicationLabel of KeyChainActivity.java, there is a possible way to trick the user into approving access to certificates due to misleading or insufficient UI. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In multiple locations, misleading UI due to obfuscation could lead to local escalation of privilege.

In multiple locations, a way to execute code in the launcher process due to an over-privileged shell user could lead to local escalation of privilege.

In multiple functions of PackageInstallerService.java, a missing permission check allows installing unverified apps, leading to local escalation of privilege.

In getCallingAppLabel of CertInstaller.java, there is a possible way to hide a sensitive security dialogue due to misleading or insufficient UI. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In approvalLevelForDomainInternal of DomainVerificationService.java, there is a possible way to hijack an arbitrary app link 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.

In setGlobalProxy of DevicePolicyManagerService.java, there is a possible desync in persistence due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In resumeConfigurationDispatch of ActivityRecord.java, there is a possible background application launch (bal) 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.

In the validateNode function in ResourceTypes.cpp, there is a potential out-of-bounds read due to an incorrect bounds check. This could lead to local escalation of privilege without additional execution privileges. User interaction is not required for exploitation.

In multiple functions of sdp_discovery.cc, there is a possible way to achieve code execution due to a heap buffer overflow. This could lead to remote (proximal/adjacent) code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

In the bta_jv_rfcomm_connect function in bta_jv_act.cc, there is a possible bypass of bonding for a secure connection due to a logic error in the code. This could lead to local escalation of privilege without additional execution privileges. User interaction is not required for exploitation.

In startAnimation of StageCoordinator.java, a tapjacking issue due to overlay attack could lead to local escalation of privilege.

In multiple locations, there is a possible tapjacking due to a logic error in the code. This could lead to local escalation of privilege without additional execution privileges. User interaction is not required for exploitation.

In the performPreInstallChecks function in InstallRepository.kt, there is a possible way to bypass MDM policy due to a logic error in the code. This could lead to local escalation of privilege without additional execution privileges. User interaction is not required for exploitation.

In multiple locations, there is a possible way to reset user-selected permissions selections due to a permissions bypass. This could lead to local escalation of privilege without additional execution privileges. User interaction is not required for exploitation.

In functions of PipTaskOrganizer.java, there is a possible way to launch an activity from the background due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In multiple locations, there is a possible background activity launch due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.