3 ms·
I'm not just making a general statement about all bugs, but also a specific statement about how I think this bug could play out. Not only does it kill all proc
by kbenson 9y ago
I'm not just making a general statement about all bugs, but also a specific statement about how I think this bug could play out. Not only does it kill all processes under the user, but it also crashes the entire system. Both of those are interesting bugs, and have possible implications if you can cause them in interesting situations.
Can you cause some system process that happens to share the user with another, more interesting process to run a kill syscall?
Can you cause the system to crash while some more trusted process is in the middle of updating a configuration, password, or other data structure that will cause interesting effects after the system is restarted?
Both being able to cause other user processes to die, and to cause the system crash on demand as a user, are things I would consider individually as security problems just because they have a high probability of having unforeseen consequences. Having them together doubles the attack space (even if it does possibly create some problems with following through with a second action).
- eridius 9y agoKilling all processes under the user is the expected behavior of kill(-1). That's perfectly fine. Crashing the system is the bug part. From the manpage: If pid is -1: If the user has super-user privileges, the signal is sent to all processes excluding system processes and the process sending the signal. If the user is not the super user, the signal is sent to all processes with the same uid as the user, excluding the process sending the signal. No error is returned if any process could be signaled.
- kbenson 9y agoFair enough, I really should have caught that. I guess it's been longer than I thought since I had to deal with that stuff. :/ It doesn't change the point I was trying to make much though.