11–20 of 72 posts
My intention is not to offend the author by the way :). It is to remind people to understand these kind of scripts and their risks before you run them.
This is just automating running the exploit from here: https://github.com/timwr/CVE-2016-5195
I put 'root' in quotes, because technically, it isn't rooting. However, it creates a binary called 'run-as' that can execute packages as root. Not sure what the right term would be in this case.
Well if you can run any executable as root, that sure counts as rooting in my book.
I put 'root' in quotes, because technically, it isn't rooting. However, it creates a binary called 'run-as' that can execute packages as root. Not sure what the right term would be in this case.
I think this would be a "temporary root", rather than something like CF-AutoRoot that gains persistence by modifying the system itself.
Good thinking! I wonder if it will get patched soon enough
I put 'root' in quotes, because technically, it isn't rooting. However, it creates a binary called 'run-as' that can execute packages as root. Not sure what the right term would be in this case.
Maybe pseudo-sudo?
Earlier quoted context omitted.
Well if you can run any executable as root, that sure counts as rooting in my book.
Sure, but as soon as it's patched out, you're back to no root.
I put 'root' in quotes, because technically, it isn't rooting. However, it creates a binary called 'run-as' that can execute packages as root. Not sure what the right term would be in this case.
A (somewhat cringeworthy) thread on how to gain persistence via this exploit is at https://github.com/timwr/CVE-2016-5195/issues/9 I think this would be a "temporary root", rather than something like CF-AutoRoot that gains persistence by modifying the system itself.
The ironic part is that since DirtyCOW is a kernel bug they could probably modify the exploit to disable SELinux from inside the kernel (or load a module that disables SELinux). But they're just trying to use the PoC as the only thing you can get from the exploit.
I wonder how many people carelessly run a script that downloads, builds, and executed something with root access. If that zip gets compromised (i.e. The source means harm) there is no end to the pain a careless user can endure. It is like blindly copying and running shell commands you don't understand with sudo rights. My intention is not to offend the author by the way :). It is to remind people to understand these…