systemd Project systemd 245 Release Candidate 1

CPE Details

systemd Project systemd 245 Release Candidate 1
245
2022-01-28
18h03 +00:00
2022-01-28
18h09 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:systemd_project:systemd:245:rc1:*:*:*:*:*:*

Informations

Vendor

systemd_project

Product

systemd

Version

245

Update

rc1

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2023-26604 2023-03-03 00h00 +00:00 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.
7.8
High
CVE-2022-3821 2022-11-07 23h00 +00:00 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.
5.5
Medium
CVE-2021-3997 2022-08-22 22h00 +00:00 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.
5.5
Medium
CVE-2021-33910 2021-07-20 16h13 +00:00 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.
5.5
Medium
CVE-2020-13776 2020-06-03 00h05 +00:00 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.
6.7
Medium