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…

In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via a crafted optional config file

In udev in systemd before 260, local root execution can occur via malicious hardware devices and unsanitized kernel output

An exploitable denial-of-service vulnerability exists in Systemd 245

Systemd-resolved: unsigned name response in signed zone is not refused when dnssec=yes

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…

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

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

systemd: Local unprivileged user can trigger an assert

A vulnerability was found in systemd

systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace

An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c

A flaw was found in systemd

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…

systemd 37-1 does not properly handle non-existent services, which causes a denial of service (failure of login procedure)

An issue was discovered in sd-bus in systemd 239

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…

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…

An issue was discovered in systemd 253

An issue was discovered in systemd 253

An issue was discovered in systemd 253

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

Systemd-coredump: race condition that allows a local attacker to crash a suid program and gain read access to the resulting core dump

It was discovered systemd does not correctly check the content of PIDFile files before using it to kill processes

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,…

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…