In AndroidManifest.xml, there is a possible persistent denial of service due to a missing permission check. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

In NFC, there is a possible way to spoof an NFC event 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.

In MmsSmsProvider of MmsSmsProvider.java, there is a possible way to retrieve sensitive information due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

In Telecomm, there is a possible way to initiate an unauthorized phone call due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In SettingsLib, there is a possible missing permission check 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 PackageInstaller.Session#transfer of frameworks/base/services/core/java/com/android/server/pm/PackageInstallerSession.java, there is a possible memory exhaustion attack due to a logic error in the code. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

In isSlotMarkedSuccessful of BootControl.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local  information disclosure with no additional execution privileges needed. User  interaction is not needed for exploitation.

There is a possible UAF 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 dhd_prot_flowrings_pool_release of dhd_msgbuf.c, there is a possible outcof bounds write due to a missing bounds check. This could lead to localcescalation of privilege with no additional execution privileges needed. Usercinteraction is not needed for exploitation.

In Nfc::eventCallback() of Nfc.h, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In multiple places, there is a possible persistent denial of service due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

There is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In addInputMethodListener of com.android.server.inputmethod.InputMethodManagerService, there is 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.

In setAllowedCarriers of PhoneInterfaceManager.java, there is a possible way to disable carrier restrictions 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 endCallForSubscriber of PhoneInterfaceManager.java, there is a possible way to prevent access to emergency services due to a logic error in the code. This could lead to a local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

In Contacts Provider, there is a possible way to access the contacts database due to SQL injection. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

In createSessionInternal of PackageInstallerService.java, there is a possible method to remove a DPC app from a managed device without DO consent due to desync from persistence. This could lead to local escalation of privilege if a user can install a malicious app with no additional execution privileges needed. User interaction is needed for exploitation.

In sg_remove_scat of scsi/sg.c, there is a possible memory corruption due to an unusual root cause. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

In tryStartActivity of NfcDispatcher.java, there is a possible automatic special app access permission assignment due to an insecure default value. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In FrpBypassAlertActivity of FrpBypassAlertActivity.java, there is a possible way to bypass FRP 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.

In dialer service, there is a possible missing permission check. This could lead to local denial of service with no additional execution privileges.

In audio service, there is a possible missing permission check. This could lead to local escalation of privilege with no additional execution privileges.

In wlan driver, there is a possible missing permission check. This could lead to local information disclosure.

Missing Authorization vulnerability in rustdesk-client RustDesk Client rustdesk-client on Windows, MacOS, Linux, iOS, Android (Flutter URI scheme handler, config import modules) allows Application API Message Manipulation via Man-in-the-Middle. This vulnerability is associated with program files flutter/lib/common.Dart and program routines importConfig() via URI handler. This issue affects RustDesk Client: through 1.4.5.

In wlan driver, there is a possible missing permission check. This could lead to local information disclosure.

In wlan driver, there is a possible missing permission check. This could lead to local information disclosure.

In audio service, there is a possible missing permission check. This could lead to local escalation of privilege with no additional execution privileges.

In audio service, there is a possible missing permission check. This could lead to local escalation of privilege with no additional execution privileges.

In audio service, there is a possible missing permission check. This could lead to local escalation of privilege with no additional execution privileges.

In soter service, there is a possible missing permission check. This could lead to local denial of service with no additional execution privileges.

In telephony service, there is a missing permission check. This could lead to local denial of service in telephone service with no additional execution privileges needed.

In soter service, there is a possible missing permission check. This could lead to local denial of service with no additional execution privileges.

In bluetooth driver, there is a missing permission check. This could lead to local information disclosure with no additional execution privileges needed.

In telephony service, there is a possible missing permission check. This could lead to local denial of service with no additional execution privileges.

In wlan driver, there is a possible missing permission check. This could lead to local information disclosure.

In telephony service, there is a possible missing permission check. This could lead to local denial of service with no additional execution privileges.

.In srtd service, there is a possible missing permission check. This could lead to local escalation of privilege with no additional execution privileges.

In dialer service, there is a possible missing permission check. This could lead to local denial of service with no additional execution privileges.

In telephony service, there is a missing permission check. This could lead to local denial of service in telephone service with no additional execution privileges needed.

In telephony service, there is a missing permission check. This could lead to local denial of service in telephone service with no additional execution privileges needed.

In engineermode services, there is a missing permission check. This could lead to local escalation of privilege with system execution privileges needed.

In wlan driver, there is a possible missing permission check. This could lead to local information disclosure.

In telephony service, there is a missing permission check. This could lead to local information disclosure with no additional execution privileges needed.

In telephony service, there is a possible missing permission check. This could lead to local denial of service with no additional execution privileges.

In engineermode service, there is a possible missing permission check. This could lead to local denial of service with no additional execution privileges.

In soter service, there is a possible missing permission check. This could lead to local denial of service with no additional execution privileges.

In audio service, there is a possible missing permission check. This could lead to local escalation of privilege with no additional execution privileges.

In log service, there is a missing permission check. This could lead to local denial of service in log service.

In telephony service, there is a missing permission check. This could lead to local information disclosure with no additional execution privileges needed.

In dialer service, there is a possible missing permission check. This could lead to local denial of service with no additional execution privileges.