I have a Samsung SM-S120VL running Android 6.0.1 with a security patch date of October 1st, 2016.
I cross-compile the dirtyc0w exploit and run-as. I push them to /data/local/tmp using adb. I then execute dirtycow run-as /system/bin/run-as
Dirtycow is successful, I am able to overwrite the original run-as executable. ls -l shows that run-as does not have the setuid bit set. I execute run-as, I am not provided with a root shell.
I know a good bit about Linux and feel that the issue is with the setuid bit not being set. I do not know much about the Android OS though. Is there any other programs that might have the setuid bit set that I could try to overwrite using dirtyc0w? Probably not, right?
I felt I would mention this as an issue because a google search showed people recommending submitting an issue if the exploit was unsuccessful. I feel the exploit is actually working, it's just that on my phone, the setuid bit is not set on run-as.
Any suggestions on anything I can try in an attempt to gain root?
Hi,
I have a Samsung SM-S120VL running Android 6.0.1 with a security patch date of October 1st, 2016.
I cross-compile the dirtyc0w exploit and run-as. I push them to /data/local/tmp using adb. I then execute dirtycow run-as /system/bin/run-as
Dirtycow is successful, I am able to overwrite the original run-as executable. ls -l shows that run-as does not have the setuid bit set. I execute run-as, I am not provided with a root shell.
I know a good bit about Linux and feel that the issue is with the setuid bit not being set. I do not know much about the Android OS though. Is there any other programs that might have the setuid bit set that I could try to overwrite using dirtyc0w? Probably not, right?
I felt I would mention this as an issue because a google search showed people recommending submitting an issue if the exploit was unsuccessful. I feel the exploit is actually working, it's just that on my phone, the setuid bit is not set on run-as.
Any suggestions on anything I can try in an attempt to gain root?
Thank you!