Overview 18 matches · 0 in Waratek scope · 0 protected · 2 exploited · 1 CISA KEV · 7 public PoC · 3 EPSS ≥ 0.5
18matches
0in Waratek scope0.0%
0protected0.0%
2exploited11.1%
1CISA KEV5.6%
7public PoC38.9%
3EPSS ≥ 0.516.7%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
2
11.1%
Not applicable
16
88.9%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
18
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
11.1%
Working exploit published
5
27.8%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
11
61.1%
split by
peak 4 / year
20021
Not applicable1
High1
not blocked1
Working exploit published1
20030
20040
20050
20060
20070
20080
20090
20100
20110
20120
20130
20140
20151
Not applicable1
High1
not blocked1
Working exploit published1
20160
20172
Not applicable2
High2
not blocked2
No public exploit2
20181
Not applicable1
High1
not blocked1
No public exploit1
20193
Not applicable3
High3
not blocked3
Working exploit published1
No public exploit2
20201
Not applicable1
High1
not blocked1
Working exploit published1
20212
Outside Waratek scope2
High2
not blocked2
Exploited1
No public exploit1
20221
Not applicable1
High1
not blocked1
No public exploit1
20234
Not applicable4
High4
not blocked4
Exploited1
No public exploit3
20240
20251
Not applicable1
High1
not blocked1
Working exploit published1
20261
Not applicable1
High1
not blocked1
No public exploit1
2002200420062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-35535 | High | 2026-04-03 | Not applicable | No public exploit | In Sudo through 1.9.17p2 before 3e474c2, a failure of a setuid, setgid, or setgroups call, during a privilege drop before running the mailer, is not a fatal error and can lead to privilege escalation. |
| CVE-2025-32462 | High | 2025-06-30 | Not applicable | Working exploit published | Sudo before 1.9.17p1, when used with a sudoers file that specifies a host that is neither the current host nor ALL, allows listed users to execute commands on unintended machines. |
| CVE-2023-7090 | High | 2023-12-23 | Not applicable | No public exploit | A flaw was found in sudo in the handling of ipa_hostname, where ipa_hostname from /etc/sssd/sssd.conf was not propagated in sudo. Therefore, it leads to privilege mismanagement vulnerability in applications, where client hosts retain privileges even after retracting them. |
| CVE-2023-42465 | High | 2023-12-22 | Not applicable | No public exploit | Sudo before 1.9.15 might allow row hammer attacks (for authentication bypass or privilege escalation) because application logic sometimes is based on not equaling an error value (instead of equaling a success value), and because the values do not resist flips of a single bit. |
| CVE-2023-27320 | High | 2023-02-28 | Not applicable | No public exploit | Sudo before 1.9.13p2 has a double free in the per-command chroot feature. |
| CVE-2023-22809 | High | 2023-01-18 | Not applicable | Exploited | In Sudo before 1.9.12p2, the sudoedit (aka -e) feature mishandles extra arguments passed in the user-provided environment variables (SUDO_EDITOR, VISUAL, and EDITOR), allowing a local attacker to append arbitrary entries to the list of files to process. This can lead to privilege escalation. Affected versions are 1.8.0 through 1.9.12.p1. The problem exists because a user-specified editor may contain a "--" argument that defeats a protection mechanism, e.g., an EDITOR='vim -- /path/to/extra/file' value. |
| CVE-2022-43995 | High | 2022-11-02 | Not applicable | No public exploit | Sudo 1.8.0 through 1.9.12, with the crypt() password backend, contains a plugins/sudoers/auth/passwd.c array-out-of-bounds error that can result in a heap-based buffer over-read. This can be triggered by arbitrary local users with access to Sudo by entering a password of seven characters or fewer. The impact could vary depending on the system libraries, compiler, and processor architecture. |
| CVE-2021-3156 | High | 2021-01-26 | Outside Waratek scope | Exploited | Sudo before 1.9.5p2 contains an off-by-one error that can result in a heap-based buffer overflow, which allows privilege escalation to root via "sudoedit -s" and a command-line argument that ends with a single backslash character. |
| CVE-2021-23240 | High | 2021-01-12 | Outside Waratek scope | No public exploit | selinux_edit_copy_tfiles in sudoedit in Sudo before 1.9.5 allows a local unprivileged user to gain file ownership and escalate privileges by replacing a temporary file with a symlink to an arbitrary file target. This affects SELinux RBAC support in permissive mode. Machines without SELinux are not vulnerable. |
| CVE-2019-18634 | High | 2020-01-29 | Not applicable | Working exploit published | In Sudo before 1.8.26, if pwfeedback is enabled in /etc/sudoers, users can trigger a stack-based buffer overflow in the privileged sudo process. (pwfeedback is a default setting in Linux Mint and elementary OS; however, it is NOT the default for upstream and many other packages, and would exist only if enabled by an administrator.) The attacker needs to deliver a long string to the stdin of getln() in tgetpass.c. |
| CVE-2019-18684 | High | 2019-11-04 | Not applicable | No public exploit | Sudo through 1.8.29 allows local users to escalate to root if they have write access to file descriptor 3 of the sudo process. This occurs because of a race condition between determining a uid, and the setresuid and openat system calls. The attacker can write "ALL ALL=(ALL) NOPASSWD:ALL" to /proc/#####/fd/3 at a time when Sudo is prompting for a password. NOTE: This has been disputed due to the way Linux /proc works. It has been argued that writing to /proc/#####/fd/3 would only be viable if you had permission to write to /etc/sudoers. Even with write permission to /proc/#####/fd/3, it would not help you write to /etc/sudoers |
| CVE-2005-4890 | High | 2019-11-04 | Not applicable | No public exploit | There is a possible tty hijacking in shadow 4.x before 4.1.5 and sudo 1.x before 1.7.4 via "su - user -c program". The user session can be escaped to the parent session by using the TIOCSTI ioctl to push characters into the input buffer to be read by the next process. |
| CVE-2019-14287 | High | 2019-10-17 | Not applicable | Working exploit published | In Sudo before 1.8.28, an attacker with access to a Runas ALL sudoer account can bypass certain policy blacklists and session PAM modules, and can cause incorrect logging, by invoking sudo with a crafted user ID. For example, this allows bypass of !root configuration, and USER= logging, for a "sudo -u \#$((0xffffffff))" command. |
| CVE-2016-7076 | High | 2018-05-29 | Not applicable | No public exploit | sudo before version 1.8.18p1 is vulnerable to a bypass in the sudo noexec restriction if application run via sudo executed wordexp() C library function with a user supplied argument. A local user permitted to run such application via sudo with noexec restriction could possibly use this flaw to execute arbitrary commands with elevated privileges. |
| CVE-2015-8239 | High | 2017-10-10 | Not applicable | No public exploit | The SHA-2 digest support in the sudoers plugin in sudo after 1.8.7 allows local users with write permissions to parts of the called command to replace them before it is executed. |
| CVE-2017-1000368 | High | 2017-06-05 | Not applicable | No public exploit | Todd Miller's sudo version 1.8.20p1 and earlier is vulnerable to an input validation (embedded newlines) in the get_process_ttyname() function resulting in information disclosure and command execution. |
| CVE-2015-5602 | High | 2015-11-17 | Not applicable | Working exploit published | sudoedit in Sudo before 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, as demonstrated by "/home/*/*/file.txt." |
| CVE-2002-0184 | High | 2002-05-16 | Not applicable | Working exploit published | Sudo before 1.6.6 contains an off-by-one error that can result in a heap-based buffer overflow that may allow local users to gain root privileges via special characters in the -p (prompt) argument, which are not properly expanded. |