Overview 58 matches · 1 in Waratek scope · 1 protected · 0 exploited · 0 CISA KEV · 7 public PoC · 1 EPSS ≥ 0.5
58matches
1in Waratek scope1.7%
1protected1.7%
0exploited0.0%
0CISA KEV0.0%
7public PoC12.1%
1EPSS ≥ 0.51.7%
Protected by Waratek
1
1.7%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
12
20.7%
Not applicable
45
77.6%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
1.7%
partly blocked
0
0.0%
not blocked
57
98.3%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 11 / year
20121
Not applicable1
Low1
not blocked1
No public exploit1
20135
Not applicable5
High1
Medium3
Low1
not blocked5
No public exploit5
20141
Not applicable1
Medium1
not blocked1
No public exploit1
20150
20162
Not applicable2
Medium2
not blocked2
No public exploit2
20176
Not applicable6
Critical2
High4
not blocked6
Working exploit published1
Forecast only1
No public exploit4
20186
Outside Waratek scope1
Not applicable5
High5
Medium1
not blocked6
Working exploit published3
No public exploit3
201911
Outside Waratek scope6
Not applicable5
Critical1
High5
Medium4
Low1
not blocked11
Working exploit published3
No public exploit8
20205
Outside Waratek scope2
Not applicable3
High2
Medium3
not blocked5
No public exploit5
20212
Outside Waratek scope2
Medium2
not blocked2
No public exploit2
20225
Protected by Waratek1
Outside Waratek scope1
Not applicable3
Critical1
High1
Medium3
blocked by ARMR today1
not blocked4
No public exploit5
20236
Not applicable6
High1
Medium5
not blocked6
Proof of concept only2
No public exploit4
20240
20251
Not applicable1
Medium1
not blocked1
Proof of concept only1
20267
Not applicable7
High1
Medium5
Low1
not blocked7
Proof of concept only2
No public exploit5
20122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-40228 | Low | 2026-04-10 | Not applicable | Proof of concept only | In systemd 259, systemd-journald can send ANSI escape sequences to the terminals of arbitrary users when a "logger -p emerg" command is executed, if ForwardToWall=yes is set. |
| CVE-2026-40227 | Medium | 2026-04-10 | Not applicable | No public exploit | In systemd 260 before 261, a local unprivileged user can trigger an assert via an IPC API call with an array or map that has a null element. |
| CVE-2026-40226 | Medium | 2026-04-10 | Not applicable | Proof of concept only | In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via a crafted optional config file. |
| CVE-2026-40225 | Medium | 2026-04-10 | Not applicable | No public exploit | In udev in systemd before 260, local root execution can occur via malicious hardware devices and unsanitized kernel output. |
| CVE-2026-40224 | High | 2026-04-10 | Not applicable | No public exploit | In systemd 259 before 260, there is local privilege escalation in systemd-machined because varlink can be used to reach the root namespace. |
| CVE-2026-40223 | Medium | 2026-04-10 | Not applicable | No public exploit | In systemd 258 before 260, a local unprivileged user can trigger an assert when a Delegate=yes and User=<unset> unit exists and is running. |
| CVE-2026-29111 | Medium | 2026-03-23 | Not applicable | No public exploit | systemd, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. No known workarounds are available. |
| CVE-2025-4598 | Medium | 2025-05-30 | Not applicable | Proof of concept only | A vulnerability was found in systemd-coredump. This flaw allows an attacker to force a SUID process to crash and replace it with a non-SUID binary to access the original's privileged process coredump, allowing the attacker to read sensitive data, such as /etc/shadow content, loaded by the original process. A SUID binary or process has a special type of permission, which allows the process to run with the file owner's permissions, regardless of the user executing the binary. This allows the process to access more restricted data than unprivileged users or processes would be able to. An attacker can leverage this flaw by forcing a SUID process to crash and force the Linux kernel to recycle the process PID before systemd-coredump can analyze the /proc/pid/auxv file. If the attacker wins the race condition, they gain access to the original's SUID process coredump file. They can read sensitive content loaded into memory by the original binary, affecting data confidentiality. |
| CVE-2023-7008 | Medium | 2023-12-23 | Not applicable | No public exploit | A vulnerability was found in systemd-resolved. This issue may allow systemd-resolved to accept records of DNSSEC-signed domains even when they have no signature, allowing man-in-the-middles (or the upstream DNS resolver) to manipulate records. |
| CVE-2023-31439 | Medium | 2023-06-13 | Not applicable | No public exploit | An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability." |
| CVE-2023-31438 | Medium | 2023-06-13 | Not applicable | No public exploit | An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability." |
| CVE-2023-31437 | Medium | 2023-06-13 | Not applicable | No public exploit | An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability." |
| CVE-2023-26604 | High | 2023-03-03 | Not applicable | Proof of concept only | systemd before 247 does not adequately block local privilege escalation for some Sudo configurations, e.g., plausible sudoers files in which the "systemctl status" command may be executed. Specifically, systemd does not set LESSSECURE to 1, and thus other programs may be launched from the less program. This presents a substantial security risk when running systemctl from Sudo, because less executes as root when the terminal size is too small to show the complete systemctl output. |
| CVE-2022-4415 | Medium | 2023-01-11 | Not applicable | Proof of concept only | A vulnerability was found in systemd. This security flaw can cause a local information leak due to systemd-coredump not respecting the fs.suid_dumpable kernel setting. |
| CVE-2022-45873 | Medium | 2022-11-23 | Not applicable | No public exploit | systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace. This occurs in parse_elf_object in shared/elf-util.c. The exploitation methodology is to crash a binary calling the same function recursively, and put it in a deeply nested directory to make its backtrace large enough to cause the deadlock. This must be done 16 times when MaxConnections=16 is set for the systemd/units/systemd-coredump.socket file. |
| CVE-2022-3821 | Medium | 2022-11-08 | Not applicable | No public exploit | An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service. |
| CVE-2022-2526 | Critical | 2022-09-09 | Outside Waratek scope | No public exploit | A use-after-free vulnerability was found in systemd. This issue occurs due to the on_stream_io() function and dns_stream_complete() function in 'resolved-dns-stream.c' not incrementing the reference counting for the DnsStream object. Therefore, other functions and callbacks called can dereference the DNSStream object, causing the use-after-free when the reference is still used later. |
| CVE-2021-3997 | Medium | 2022-08-23 | Not applicable | No public exploit | A flaw was found in systemd. An uncontrolled recursion in systemd-tmpfiles may lead to a denial of service at boot time when too many nested directories are created in /tmp. |
| CVE-2022-26477 | High | 2022-06-27 | Protected by Waratek | No public exploit | The Security Team noticed that the termination condition of the for loop in the readExternal method is a controllable variable, which, if tampered with, may lead to CPU exhaustion. As a fix, we added an upper bound and termination condition in the read and write logic. We classify it as a "low-priority but useful improvement". SystemDS is a distributed system and needs to serialize/deserialize data but in many code paths (e.g., on Spark broadcast/shuffle or writing to sequence files) the byte stream is anyway protected by additional CRC fingerprints. In this particular case though, the number of decoders is upper-bounded by twice the number of columns, which means an attacker would need to modify two entries in the byte stream in a consistent manner. By adding these checks robustness was strictly improved with almost zero overhead. These code changes are available in versions higher than 2.2.1. |
| CVE-2021-33910 | Medium | 2021-07-20 | Outside Waratek scope | No public exploit | basic/unit-name.c in systemd prior to 246.15, 247.8, 248.5, and 249.1 has a Memory Allocation with an Excessive Size Value (involving strdupa and alloca for a pathname controlled by a local attacker) that results in an operating system crash. |
| CVE-2020-13529 | Medium | 2021-05-10 | Outside Waratek scope | No public exploit | An exploitable denial-of-service vulnerability exists in Systemd 245. A specially crafted DHCP FORCERENEW packet can cause a server running the DHCP client to be vulnerable to a DHCP ACK spoofing attack. An attacker can forge a pair of FORCERENEW and DCHP ACK packets to reconfigure the server. |
| CVE-2020-26261 | High | 2020-12-09 | Not applicable | No public exploit | jupyterhub-systemdspawner enables JupyterHub to spawn single-user notebook servers using systemd. In jupyterhub-systemdspawner before version 0.15 user API tokens issued to single-user servers are specified in the environment of systemd units. These tokens are incorrectly accessible to all users. In particular, the-littlest-jupyterhub is affected, which uses systemdspawner by default. This is patched in jupyterhub-systemdspawner v0.15 |
| CVE-2020-13776 | Medium | 2020-06-03 | Outside Waratek scope | No public exploit | systemd through v245 mishandles numerical usernames such as ones composed of decimal digits or 0x followed by hex digits, as demonstrated by use of root privileges when privileges of the 0x0 user account were intended. NOTE: this issue exists because of an incomplete fix for CVE-2017-1000082. |
| CVE-2020-1712 | High | 2020-03-31 | Not applicable | No public exploit | A heap use-after-free vulnerability was found in systemd before version v245-rc1, where asynchronous Polkit queries are performed while handling dbus messages. A local unprivileged attacker can abuse this flaw to crash systemd services or potentially execute code and elevate their privileges, by sending specially crafted dbus messages. |
| CVE-2012-1101 | Medium | 2020-03-11 | Not applicable | No public exploit | systemd 37-1 does not properly handle non-existent services, which causes a denial of service (failure of login procedure). |
| CVE-2019-20386 | Medium | 2020-01-21 | Outside Waratek scope | No public exploit | An issue was discovered in button_open in login/logind-button.c in systemd before 243. When executing the udevadm trigger command, a memory leak may occur. |
| CVE-2018-21029 | Critical | 2019-10-30 | Not applicable | No public exploit | systemd 239 through 245 accepts any certificate signed by a trusted certificate authority for DNS Over TLS. Server Name Indication (SNI) is not sent, and there is no hostname validation with the GnuTLS backend. NOTE: This has been disputed by the developer as not a vulnerability since hostname validation does not have anything to do with this issue (i.e. there is no hostname to be sent) |
| CVE-2019-15718 | Medium | 2019-09-04 | Not applicable | No public exploit | In systemd 240, bus_open_system_watch_bind_with_description in shared/bus-util.c (as used by systemd-resolved to connect to the system D-Bus instance), calls sd_bus_set_trusted, which disables access controls for incoming D-Bus messages. An unprivileged user can exploit this by executing D-Bus methods that should be restricted to privileged users, in order to change the system's DNS resolver settings. |
| CVE-2018-20839 | Medium | 2019-05-17 | Outside Waratek scope | No public exploit | systemd 242 changes the VT1 mode upon a logout, which allows attackers to read cleartext passwords in certain circumstances, such as watching a shutdown, or using Ctrl-Alt-F1 and Ctrl-Alt-F2. This occurs because the KDGKBMODE (aka current keyboard mode) check is mishandled. |
| CVE-2019-3844 | High | 2019-04-26 | Outside Waratek scope | Working exploit published | It was discovered that a systemd service that uses DynamicUser property can get new privileges through the execution of SUID binaries, which would allow to create binaries owned by the service transient group with the setgid bit set. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the GID will be recycled. |
| CVE-2019-3843 | High | 2019-04-26 | Outside Waratek scope | Working exploit published | It was discovered that a systemd service that uses DynamicUser property can create a SUID/SGID binary that would be allowed to run as the transient service UID/GID even after the service is terminated. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the UID/GID will be recycled. |
| CVE-2019-3842 | High | 2019-04-09 | Not applicable | Working exploit published | In systemd before v242-rc4, it was discovered that pam_systemd does not properly sanitize the environment before using the XDG_SEAT variable. It is possible for an attacker, in some particular configurations, to set a XDG_SEAT environment variable which allows for commands to be checked against polkit policies using the "allow_active" element rather than "allow_any". |
| CVE-2019-6454 | Medium | 2019-03-21 | Not applicable | No public exploit | An issue was discovered in sd-bus in systemd 239. bus_process_object() in libsystemd/sd-bus/bus-objects.c allocates a variable-length stack buffer for temporarily storing the object path of incoming D-Bus messages. An unprivileged local user can exploit this by sending a specially crafted message to PID1, causing the stack pointer to jump over the stack guard pages into an unmapped memory region and trigger a denial of service (systemd PID1 crash and kernel panic). |
| CVE-2018-16888 | Medium | 2019-01-14 | Outside Waratek scope | No public exploit | It was discovered systemd does not correctly check the content of PIDFile files before using it to kill processes. When a service is run from an unprivileged user (e.g. User field set in the service file), a local attacker who is able to write to the PIDFile of the mentioned service may use this flaw to trick systemd into killing other services and/or privileged processes. Versions before v237 are vulnerable. |
| CVE-2018-16866 | Low | 2019-01-11 | Outside Waratek scope | No public exploit | An out of bounds read was discovered in systemd-journald in the way it parses log messages that terminate with a colon ':'. A local attacker can use this flaw to disclose process memory data. Versions from v221 to v239 are vulnerable. |
| CVE-2018-16865 | High | 2019-01-11 | Outside Waratek scope | No public exploit | An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the journal socket. A local attacker, or a remote one if systemd-journal-remote is used, may use this flaw to crash systemd-journald or execute code with journald privileges. Versions through v240 are vulnerable. |
| CVE-2018-16864 | High | 2019-01-11 | Not applicable | No public exploit | An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when a program with long command line arguments calls syslog. A local attacker may use this flaw to crash systemd-journald or escalate his privileges. Versions through v240 are vulnerable. |
| CVE-2018-15688 | High | 2018-10-26 | Not applicable | No public exploit | A buffer overflow vulnerability in the dhcp6 client of systemd allows a malicious dhcp6 server to overwrite heap memory in systemd-networkd. Affected releases are systemd: versions up to and including 239. |
| CVE-2018-15687 | High | 2018-10-26 | Not applicable | Working exploit published | A race condition in chown_one() of systemd allows an attacker to cause systemd to set arbitrary permissions on arbitrary files. Affected releases are systemd versions up to and including 239. |
| CVE-2018-15686 | High | 2018-10-26 | Outside Waratek scope | Working exploit published | A vulnerability in unit_deserialize of systemd allows an attacker to supply arbitrary state across systemd re-execution via NotifyAccess. This can be used to improperly influence systemd execution and possibly lead to root privilege escalation. Affected releases are systemd versions up to and including 239. |
| CVE-2018-1049 | Medium | 2018-02-16 | Not applicable | No public exploit | In systemd prior to 234 a race condition exists between .mount and .automount units such that automount requests from kernel may not be serviced by systemd resulting in kernel holding the mountpoint and any processes that try to use said mount will hang. A race condition like this may lead to denial of service, until mount points are unmounted. |
| CVE-2018-6954 | High | 2018-02-13 | Not applicable | No public exploit | systemd-tmpfiles in systemd through 237 mishandles symlinks present in non-terminal path components, which allows local users to obtain ownership of arbitrary files via vectors involving creation of a directory and a file under that directory, and later replacing that directory with a symlink. This occurs even if the fs.protected_symlinks sysctl is turned on. |
| CVE-2017-18078 | High | 2018-01-29 | Not applicable | Working exploit published | systemd-tmpfiles in systemd before 237 attempts to support ownership/permission changes on hardlinked files even if the fs.protected_hardlinks sysctl is turned off, which allows local users to bypass intended access restrictions via vectors involving a hard link to a file for which the user lacks write access, as demonstrated by changing the ownership of the /etc/passwd file. |
| CVE-2017-15908 | High | 2017-10-26 | Not applicable | No public exploit | In systemd 223 through 235, a remote DNS server can respond with a custom crafted DNS NSEC resource record to trigger an infinite loop in the dns_packet_read_type_window() function of the 'systemd-resolved' service and cause a DoS of the affected service. |
| CVE-2015-7510 | Critical | 2017-09-25 | Not applicable | No public exploit | Stack-based buffer overflow in the getpwnam and getgrnam functions of the NSS module nss-mymachines in systemd. |
| CVE-2017-1000082 | Critical | 2017-07-07 | Not applicable | No public exploit | systemd v233 and earlier fails to safely parse usernames starting with a numeric digit (e.g. "0day"), running the service in question with root privileges rather than the user intended. |
| CVE-2017-9445 | High | 2017-06-28 | Not applicable | Forecast only | In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that's too small. A malicious DNS server can exploit this via a response with a specially crafted TCP payload to trick systemd-resolved into allocating a buffer that's too small, and subsequently write arbitrary data beyond the end of it. |
| CVE-2017-9217 | High | 2017-05-24 | Not applicable | No public exploit | systemd-resolved through 233 allows remote attackers to cause a denial of service (daemon crash) via a crafted DNS response with an empty question section. |
| CVE-2016-10156 | High | 2017-01-23 | Not applicable | Working exploit published | A flaw in systemd v228 in /src/basic/fs-util.c caused world writable suid files to be created when using the systemd timers features, allowing local attackers to escalate their privileges to root. This is fixed in v229. |
| CVE-2016-7796 | Medium | 2016-10-13 | Not applicable | No public exploit | The manager_dispatch_notify_fd function in systemd allows local users to cause a denial of service (system hang) via a zero-length message received over a notify socket, which causes an error to be returned and the notification handler to be disabled. |
| CVE-2016-7795 | Medium | 2016-10-13 | Not applicable | No public exploit | The manager_invoke_notify_message function in systemd 231 and earlier allows local users to cause a denial of service (assertion failure and PID 1 hang) via a zero-length message received over a notify socket. |
| CVE-2012-0871 | Medium | 2014-04-18 | Not applicable | No public exploit | The session_link_x11_socket function in login/logind-session.c in systemd-logind in systemd, possibly 37 and earlier, allows local users to create or overwrite arbitrary files via a symlink attack on the X11 user directory in /run/user/. |
| CVE-2013-4394 | Medium | 2013-10-28 | Not applicable | No public exploit | The SetX11Keyboard function in systemd, when PolicyKit Local Authority (PKLA) is used to change the group permissions on the X Keyboard Extension (XKB) layouts description, allows local users in the group to modify the Xorg X11 Server configuration file and possibly gain privileges via vectors involving "special and control characters." |
| CVE-2013-4393 | Low | 2013-10-28 | Not applicable | No public exploit | journald in systemd, when the origin of native messages is set to file, allows local users to cause a denial of service (logging service blocking) via a crafted file descriptor. |
| CVE-2013-4392 | Medium | 2013-10-28 | Not applicable | No public exploit | systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files. |
| CVE-2013-4391 | High | 2013-10-28 | Not applicable | No public exploit | Integer overflow in the valid_user_field function in journal/journald-native.c in systemd allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a large journal data field, which triggers a heap-based buffer overflow. |
| CVE-2013-4327 | Medium | 2013-10-03 | Not applicable | No public exploit | systemd does not properly use D-Bus for communication with a polkit authority, which allows local users to bypass intended access restrictions by leveraging a PolkitUnixProcess PolkitSubject race condition via a (1) setuid process or (2) pkexec process, a related issue to CVE-2013-4288. |
| CVE-2012-1174 | Low | 2012-07-12 | Not applicable | No public exploit | The rm_rf_children function in util.c in the systemd-logind login manager in systemd before 44, when logging out, allows local users to delete arbitrary files via a symlink attack on unspecified files, related to "particular records related with user session." |