You also mention "arbitrary commands" while any config that allows "arbitrary commands" as ALL, !root is already almost certainly vulnerable per se and a terrible idea and nobody should be doing that.
-
-
This Tweet is unavailable.
-
If nobody should be doing that then hopefully nobody is doing that, which makes the impact minimal, which means it's your job to minimize confused panic from those who might misunderstand otherwise.
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
I had at least 5 people link me the sudo bug, some directly via your article, because they though it was some huge security hole affecting many Linux systems.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @unix_root and
Some of them even ran their own confused tests and thought it was really that bad, because sudoers is confusing and they didn't understand exactly what config they needed to have. They often accidentally gave themselves ALL outright.
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
Honestly, you didn't do a great job of conveying the details. The most confusing bit is where you go straight from ALL to "in a specific scenario where you have been allowed to run a specific, or any, command as any other user except the root"
1 reply 0 retweets 0 likes -
Replying to @marcan42 @unix_root and
That reads as "any other specific user", because the actual idea of "literally any user in the system, except for root" is so baroque that nobody thinks of it. You really need to dig into that point because it's very hard to grasp.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @unix_root and
What everyone took from that line is "a sudoers config which lets you run something as www-data lets you run it as root" which is not the case.
1 reply 0 retweets 0 likes
A much more understandable way of saying it, which the original report should've used, is "a configuration which allows users to run a command as a set of user IDs including -1, but not root" (which happens to in practice only be ALL default-any configs).
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.