Skip to content

Android software KernelSU version 0.5.7 contains a vulnerability that permits installed applications to attain root permissions, thus gaining elevated privileges on the system.

Android devices' root access is vulnerable to unauthorized acquisition due to a glitch in KernelSU 0.5.7, enabling attackers to masquerade as the manager app for potential exploitation.

Android's KernelSU version 0.5.7 contains a weakness, enabling apps to acquire root access...
Android's KernelSU version 0.5.7 contains a weakness, enabling apps to acquire root access permissions

Android software KernelSU version 0.5.7 contains a vulnerability that permits installed applications to attain root permissions, thus gaining elevated privileges on the system.

In a significant finding for the cybersecurity community, a critical vulnerability has been identified in KernelSU, a popular rooting framework used by Android users. This community-developed solution, associated with projects on platforms like GitHub linked to Android kernel development, gained notoriety for its ability to provide root access through Android kernel patching, alongside tools like APatch and SKRoot.

The security flaw, discovered in version 0.5.7, allows attackers to impersonate the system's manager application and gain root access. This exploit takes advantage of KernelSU's package-based authentication method, which relies on checking the first matching APK file in a process's file descriptor table. By manipulating file descriptor order, attackers can present the legitimate manager's APK first, bypassing signature checks in KernelSU.

This vulnerability is not without its limitations. Timing constraints limit the attack, making it practical under realistic conditions only when the attacker's app runs before the legitimate manager, such as after a reboot. The attack can be triggered automatically by using the RECEIVE_BOOT_COMPLETED permission.

The complexity of modifying kernel behavior from user space and the absence of structured security reviews contribute to these vulnerabilities. Moreover, the lack of formal security oversight is a common issue in rooting and jailbreaking frameworks, often built by independent developers.

This latest discovery underscores the need for robust security measures in these frameworks. Previous examples of such vulnerabilities include an APatch flaw and Magisk's CVE-2024-48336. Zimperium's zLabs researchers have also published an analysis on the exploitation of design flaws in authentication to bypass safeguards.

Overreliance on user-space input without validation, poor privilege isolation between apps and root-level functions, and weaknesses in password-based authentication are other common issues plaguing rooting frameworks. Insecure communication channels are also widespread, adding to the security concerns.

As the use of rooting frameworks continues to grow, it is crucial to address these vulnerabilities and ensure the safety of Android users. The cybersecurity community will continue to scrutinize these frameworks, working towards more secure solutions for the Android ecosystem.

Read also: