Lock Screen Bypass in ActivityTaskManagerService
Summary
CVE-2023-40094: In keyguardGoingAway of ActivityTaskManagerService.java, there is a possible lock screen bypass due to a missing permission check. Affects platform/frameworks/base across 6 version ranges.
>= 11:0, < 11:2023-12-01
>= 12:0, < 12:2023-12-01
>= 12L:0, < 12L:2023-12-01
>= 13:0, < 13:2023-12-01
>= 14:0, < 14:2023-12-01
>= 14-next:0, < 14-next:2023-12-01
Fixed in 14-next:2023-12-01. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The ActivityTaskManagerService is a component in the Android platform's base framework. It is responsible for managing the lifecycle of activities and tasks, as well as handling user interactions. This vulnerability affects the keyguardGoingAway method in the service, which is used to dismiss the lock screen. The issue arises from a missing permission check, allowing for a potential lock screen bypass. This vulnerability can be exploited locally, without requiring any additional execution privileges.
Vulnerability Detail
The keyguardGoingAway method in ActivityTaskManagerService.java lacks a permission check, enabling a potential lock screen bypass. An attacker could leverage this vulnerability to escalate their privileges on the device. Exploitation does not require any user interaction. The impact of this vulnerability is a local escalation of privilege, allowing an attacker to gain unauthorized access to the device's contents or perform malicious actions.
How To Fix
Minimum fixed version
14-next:2023-12-01
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability.
Conclusion
The lock screen bypass vulnerability in ActivityTaskManagerService poses a significant risk as it allows for unauthorized access to a device's contents. It is crucial to apply the recommended fix by updating to the latest version of the Android platform's base framework. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for platform/frameworks/base →
FAQ
The impact of this vulnerability is a local escalation of privilege, allowing an attacker to bypass the lock screen and gain unauthorized access to the device's contents or perform malicious actions.
No, this vulnerability can be exploited locally without requiring any user interaction.
This vulnerability affects Android versions 11, 12, 12L, 13, and 14.
Yes, a fix has been implemented in the Android platform's base framework. It is recommended to update to the latest version to mitigate this issue.
You can find more information about this vulnerability in the Android Open Source Vulnerabilities database. Please refer to the provided source link for detailed information.
Related vulnerabilities
Recent vulnerabilities recorded for platform/frameworks/base.