Fix vulnerability in CallRedirectionService.
Currently when the CallRedirectionService binding died, we didn't do anything, which cause malicious app start activities even not run in the background by implementing a CallRedirectionService and overriding the onPlaceCall method to schedule a activity start job in an independent process and then kill itself. In that way, the activity can still start after the CallRedirectionService died. Fix this by unbinding the service when the binding died. Bug: b/289809991 Test: Using testapp provided in bug to make sure the test activity can't be started Change-Id: I065d361b83700474a1efab2a75928427ee0a14ba
Loading
-
mentioned in commit 1637f8e3
-
mentioned in commit 72e92682
-
mentioned in commit a55cc01a
-
mentioned in commit d24ae916
-
mentioned in commit 39828d2e
-
mentioned in commit 8a92a8f0
-
mentioned in commit 05394e9b
-
mentioned in commit 72265bc0
-
mentioned in commit b29cb7c6
-
mentioned in commit c6b14b27
-
mentioned in commit 22a0c50b
-
mentioned in commit b0922de3
-
mentioned in commit af00c204
-
mentioned in commit db5a9dbe
Please register or sign in to comment