| |||||||||||||
Umbrella 0.7Umbrella 0.7Posted May 5, 2005 4:02 UTC (Thu) by tzafrir (subscriber, #11501)Parent article: Umbrella 0.7
note that on just about any linux system you don't need to create a new binary to do damage. If you can execute some arbitrary code, you can dump a shell scrpt to a file and use /bin/sh to "execute" it. Umbrealla only sees an execution of the stnadard signed system binary /bin/sh.
(Log in to post comments)
Umbrella 0.7 Posted May 5, 2005 9:12 UTC (Thu) by rjw (guest, #10415) [Link] Remember that processes inherit the restrictions of their parent process.So if you can "execute some arbitrary code", you can already do everything that you could do by spawning a shell. The danger is when there is a privilege *granting* mechanism : suid, filesystem caps, and some selinux policies. That isn't present AFAIK.
This is only about restrictions. What is very interesting is the signed binary thing: even if you mount the filesystem on another machine and bypass filesystem security, you won;t be able to replace a choice binary with an updated or modified version.
|
|||||||||||||