You must log in or register to comment.
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.
This wouldn’t apply to Debian derived distros (e.g. DietPi). I am assuming the fix will backported to the version of sudo shipping with bookworm.
Why wouldn’t this apply?
One day in the future the later version of sudo would become available…?
I am assuming the fix for the second vulnerability will be backported to the older version in bookworn; 13p1 if I remember correctly.
I’ve seen theme backport security to older releases of much less important software.
Already patched and available via updates.
doasI 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.
Ping, not an expert but at least my opinion
sudo-rsIs 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)
deleted by creator
