In onNullBinding of HostEmulationManager.java, there is a possible way to launch an activity from the background 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 needed for exploitation.
Weakness
The product attempts to drop privileges but does not check or incorrectly checks to see if the drop succeeded.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Android | 14.0 (including) | 14.0 (including) | |
| Android | 15.0 (including) | 15.0 (including) | |
| Android | 16.0 (including) | 16.0 (including) | |
| Android | 16.0-qpr2_beta_1 (including) | 16.0-qpr2_beta_1 (including) | |
| Android | 16.0-qpr2_beta_2 (including) | 16.0-qpr2_beta_2 (including) | |
| Android | 16.0-qpr2_beta_3 (including) | 16.0-qpr2_beta_3 (including) |
Potential Mitigations
- Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.