Sudo vulnerabilities

Sudo through version 1.9.17p2 fails to apply intercept policy checks to the execveat system call in ptrace-based intercept mode. Users permitted to run specific commands can execute denied programs by calling execveat directly or through fexecve, bypassing policy enforcement and logging.

Todd Miller's sudo version 1.8.20p1 and earlier is vulnerable to input validation (embedded newlines) in the get_process_ttyname() function resulting in information disclosure and command execution.

Sudo versions before 1.8.15 on Linux contain a vulnerability that may allow local users to bypass noexec command restrictions via applications calling the system or popen functions.

An issue was discovered in certain Apple products, including macOS before 10.12.4, related to the 'sudo' component. It allows remote authenticated users to gain privileges by leveraging membership in the admin group on a network directory server.

A vulnerability in sudoedit before version 1.8.15 allows local users to gain privileges via a symlink attack on a file whose full path is defined using multiple wildcards in /etc/sudoers.

In Sudo up to version 1.9.17p2 before commit 3e474c2, a failure of setuid, setgid, or setgroups calls during privilege drop before running the mailer is not a fatal error, which can lead to privilege escalation.

A vulnerability in Sudo before version 1.9.17p1 allows listed users in the sudoers file to execute commands on unintended machines when the file specifies a host that is neither the current host nor ALL.

Sudo version 1.5 on Debian Linux 2.1 and Red Hat 6.0 allows local users to determine the existence of arbitrary files by attempting to execute the target filename as a program, which generates different error messages when the file does not exist.

Sudo versions 1.5.x allow local users to execute arbitrary commands via a .. (dot dot) attack.