Some of these capabilities seem so obviously and trivially equivalent to having uid 0 that I wonder if I'm missing something. For example, in what cases would CAP_SET_UID or CAP_CHOWN be useful? Surely you may as well be running as root already.
Spengler: False Boundaries and Arbitrary Code Execution
Posted Jan 6, 2011 17:49 UTC (Thu) by unBrice (guest, #72229)
[Link]
You might be inside a chroot-like and only have access to your own files on a filesystem mounted with nosuid,
Spengler: False Boundaries and Arbitrary Code Execution
Posted Jan 6, 2011 19:24 UTC (Thu) by spender (subscriber, #23067)
[Link]
chroot doesn't matter: in 2002 I wrote in the French MISC magazine 11 ways to break out of a chroot jail. One of them applies here: chroot doesn't matter if you have CAP_SETUID, in fact CAP_SETUID is basically equivalent to CAP_SYS_PTRACE. If i can change to any UID, then I can effectively ptrace any process (including those running outside of the chroot) giving me full control of the host system.
-Brad
Spengler: False Boundaries and Arbitrary Code Execution
Posted Jan 7, 2011 8:23 UTC (Fri) by job (guest, #670)
[Link]
Is this article online?
Spengler: False Boundaries and Arbitrary Code Execution
Posted Jan 7, 2011 11:38 UTC (Fri) by Aissen (subscriber, #59976)
[Link]