Closed aidanbh closed 8 years ago
It doesn't look like run-as is setuid on my device (but how else would it work?
-rwxr-x--- root shell 9444 2016-06-24 15:13 run-as
Linux capabilities is how the UID can be set without the setuid bit.
@bithakr I am getting the same issue. I get the same permission in /system/bin for run-as, even after setting it to 777 in /data/local/tmp.
Edit: I also have to set dirtycow file to 777 in /data/local/tmp for this PoC to run, otherwise I get "can't execute: Permission denied." I am using a Verizon SnapDragon Galaxy S7 Edge by the way.
@bithakr it looks like the device is vulnerable but I don't think it has linux capabilities (< 4.2?). Maybe you can try https://github.com/timwr/CVE-2016-5195/tree/oldcow (or just comment out the capset stuff in run-as.c). Many thanks
@timwr That makes sense. I found another way to root my device but I'll try your suggestion to see if it works. It doesn't have Linux capabilities. The base OS in Android 5.0.1 - it runs FireOS 5.3.1.
My device hardreboots as soon as the exploit finishes, leading to the following output: Any suggestions?