Balance

**Name of the Vulnerable Software and Affected Versions** ImsService versions prior to SMR Sep-2025 Release 1 **Description** An improper access control issue exists in ImsService. This allows local attackers to utilize privileged APIs. **Recommendations** Update ImsService to SMR Sep-2025 Release 1 or later.

**Name of the Vulnerable Software and Affected Versions** Android versions prior to SMR Sep-2025 Release 1 **Description** The improper handling of insufficient permission in the AppPrelaunchManagerService allows local attackers to execute arbitrary applications in the background. **Recommendations** Update to SMR Sep-2025 Release 1 or later.

**Name of the Vulnerable Software and Affected Versions** System UI versions prior to SMR Sep-2025 Release 1 **Description** Improper handling of insufficient permission in System UI allows local attackers to send arbitrary replies to messages from the cover display. **Recommendations** Update System UI to SMR Sep-2025 Release 1 or later.

**Name of the Vulnerable Software and Affected Versions** MARsExemptionManager versions prior to SMR Sep-2025 Release 1 **Description** Improper access control in MARsExemptionManager allows local attackers to be excluded from background execution management. **Recommendations** Update MARsExemptionManager to SMR Sep-2025 Release 1 or later.

**Name of the Vulnerable Software and Affected Versions** sepunion service versions prior to SMR May-2025 Release 1 **Description** The issue is related to improper handling of insufficient permission or privileges in the sepunion service, allowing local privileged attackers to access files with system privilege. This can lead to privilege escalation. **Recommendations** For versions prior to SMR May-2025 Release 1, update to SMR May-2025 Release 1 or later to resolve the issue. As a temporary workaround, consider restricting access to sensitive files and directories to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** CocktailBarService versions prior to SMR May-2025 Release 1 **Description** The issue is related to the improper handling of insufficient permissions in CocktailBarService, allowing local attackers to use the privileged API. This enables local attackers to exploit the vulnerability. **Recommendations** For versions prior to SMR May-2025 Release 1, consider restricting access to the privileged API until a patch is available. As a temporary workaround, review and adjust the permission settings in CocktailBarService to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** DualDarManagerProxy versions prior to SMR Sep-2024 Release 1 **Description** The issue is related to the incorrect use of a privileged API in DualDarManagerProxy, allowing local attackers to access privileged APIs related to Knox without a proper license. This flaw enables local privilege escalation via the Knox API. **Recommendations** For versions prior to SMR Sep-2024 Release 1, update to the SMR Sep-2024 Release 1 or later to resolve the issue. As a temporary workaround, consider restricting access to the privileged APIs related to Knox until a patch is available.

**Name of the Vulnerable Software and Affected Versions** DualDarManagerProxy versions prior to SMR Sep-2024 Release 1 **Description** The issue is related to improper access control in DualDarManagerProxy, allowing local attackers to cause a local permanent denial of service. **Recommendations** For versions prior to SMR Sep-2024 Release 1, update to SMR Sep-2024 Release 1 or later to resolve the issue. As a temporary workaround, consider restricting access to the DualDarManagerProxy to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** KnoxMiscPolicy versions prior to SMR Sep-2024 Release 1 **Description** The issue is related to improper handling of insufficient permissions, allowing local attackers to access sensitive data. This could potentially lead to unauthorized access to confidential information. **Recommendations** For versions prior to SMR Sep-2024 Release 1, update to the SMR Sep-2024 Release 1 or later to resolve the issue. As a temporary workaround, consider restricting access to sensitive data until the update is applied.

**Name of the Vulnerable Software and Affected Versions** PaymentManagerService versions prior to SMR Aug-2024 Release 1 **Description** The issue is related to improper access control in the PaymentManagerService, allowing local attackers to bypass restrictions on starting services from the background. This could potentially lead to unauthorized access or actions within the system. **Recommendations** For versions prior to SMR Aug-2024 Release 1, update to the SMR Aug-2024 Release 1 or later to resolve the issue. As a temporary workaround, consider restricting access to the PaymentManagerService to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** LedCoverService versions prior to SMR Aug-2024 Release 1 **Description** The issue is related to improper access control in the LedCoverService, allowing local attackers to bypass restrictions on starting services from the background. **Recommendations** For versions prior to SMR Aug-2024 Release 1, update to the SMR Aug-2024 Release 1 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** CocktailBarService versions prior to SMR May-2024 Release 1 **Description** The issue is related to an improper access control vulnerability in the `startListening` function of the CocktailBarService. This vulnerability allows local attackers to access information of the current application. **Recommendations** For versions prior to SMR May-2024 Release 1, as a temporary workaround, consider disabling the `startListening` function of the CocktailBarService until a patch is available. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** SmartThings versions prior to 1.8.13.22 **Description** The issue is related to improper verification of intent by a broadcast receiver, allowing local attackers to access testing configuration. **Recommendations** For versions prior to 1.8.13.22, update to version 1.8.13.22 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** StorageManagerService versions prior to SMR Apr-2024 Release 1 **Description** The issue is related to an Improper Access Control vulnerability. It allows local attackers to bypass security and read sdcard information. **Recommendations** For versions prior to SMR Apr-2024 Release 1, update to the SMR Apr-2024 Release 1 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** AppLock versions prior to SMR Mar-2024 Release 1 **Description** The issue is related to an incorrect default permission in AppLock, allowing local attackers to configure AppLock settings. This could potentially lead to unauthorized access or changes to the settings. **Recommendations** For versions prior to SMR Mar-2024 Release 1, update to SMR Mar-2024 Release 1 or later to resolve the issue. As a temporary workaround, consider restricting access to AppLock settings to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** libsec-ril versions prior to SMR Nov-2023 Release 1 **Description** The issue is related to an improper input validation vulnerability in the ProcessWriteFile function of libsec-ril. This vulnerability allows local attackers to expose sensitive information. **Recommendations** For versions prior to SMR Nov-2023 Release 1, update to SMR Nov-2023 Release 1 or later to resolve the issue. As a temporary workaround, consider restricting access to the ProcessWriteFile function to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Telecom versions prior to SMR Aug-2023 Release 1 **Description** The issue is related to improper access control, allowing local attackers to call the "endCall API" without permission. This can be exploited by attackers to potentially disrupt or manipulate call functionality. **Recommendations** For versions prior to SMR Aug-2023 Release 1, consider restricting access to the "endCall API" until a patch is available. As a temporary workaround, disabling the API or limiting its functionality can help minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** libsec-ril versions prior to SMR Aug-2023 Release 1 **Description** The issue is related to an out-of-bounds write in the `DoOemFactorySendFactoryBypassCommand` of `libsec-ril`, allowing a local attacker to execute arbitrary code. **Recommendations** For versions prior to SMR Aug-2023 Release 1, update to the SMR Aug-2023 Release 1 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** libsec-ril versions prior to SMR Aug-2023 Release 1 **Description** The issue is related to an out-of-bounds write in the `MakeUiccAuthForOem` function of `libsec-ril`, allowing a local attacker to execute arbitrary code. **Recommendations** For versions prior to SMR Aug-2023 Release 1, update to the SMR Aug-2023 Release 1 or later to resolve the issue. As a temporary workaround, consider restricting access to the `MakeUiccAuthForOem` function until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Telecom versions prior to SMR Aug-2023 Release 1 **Description** The issue is related to improper access control, allowing local attackers to call the "silenceRinger API" without permission. **Recommendations** For versions prior to SMR Aug-2023 Release 1, update to SMR Aug-2023 Release 1 or later to resolve the issue. As a temporary workaround, consider restricting access to the "silenceRinger API" until a patch is available.