Published: 14 April 2017
sudo_noexec.so in Sudo before 1.8.15 on Linux might allow local users to bypass intended noexec command restrictions via an application that calls the (1) system or (2) popen function.
CVSS 3 base score: 7.0
Launchpad, Ubuntu, Debian
|Ubuntu 21.04 (Hirsute Hippo)||
|Ubuntu 20.10 (Groovy Gorilla)||
|Ubuntu 20.04 LTS (Focal Fossa)||
|Ubuntu 18.04 LTS (Bionic Beaver)||
|Ubuntu 16.04 LTS (Xenial Xerus)||
|Ubuntu 14.04 ESM (Trusty Tahr)||
I'm marking this negligible because this feature seems doomed to failure in the general case. Any sort of memory-protection flaws in the target process, or ability to execute system calls directly, or programs that don't use the standard C libraries, etc. won't be affected by this feature. If you rely upon this feature I suggest instead seccomp2-based filters to disable the execve() and execveat() system calls at the kernel interface or AppArmor (or other MAC system) to restrict which executables can be executed.