As far as mitigation is concerned, the only thing you need to do is to confirm that your system's sudo version is at least version 1.9.17p1 or later, which can be done with the command sudo -V. If your version is older than 1.9.17p1, update immediately.
post
I keep seeing people promote doas, but is it really any more secure than sudo? besides just having less eyes on it?
sudo has a bunch of commands and features nobody (except the person who implemented it) has ever used, giving it quite a large surface of attack. doas is meanwhile much leaner and developed by the OpenBSD community, meaning if a feature has security concerns it won't be implemented no matter how practical. sudo-rs somewhat of a middle ground between the two, not planning on implementing every single feature of sudo while keeping the same core commands and implementing the quality of life features doas doesn't like because they're insecure, and is the solution I personally use.
Subscribing to this question.
Is it better than doas?
It's an implementation of sudo in Rust (because of course) that doesn't implement every nonsense feature of the normal sudo giving it a smaller attack surface than the normal sudo while still keeping the familiar commands and ease of use (that doas is somewhat lacking)
So ‘sudo-rs’ guys were right?
The vulnerability in question would've still happened if written in rust, it was not a memory leak.
More an instance of feature creep, as the solution was to remove the functionality.
I would rather go with a completely new approach like the one of run0.
all 14 comments