Description
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.
CVSS breakdown
CVSS 3.1
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Affected products
- Debian / debian_linux10.0 – 10.0
- systemd_project / systemd246.7
References
- MISChttps://medium.com/%40zenmoviefornotification/saidov-maxim-cve-2023-26604-c1232a526ba7
- MISChttps://github.com/systemd/systemd/blob/main/NEWS#L4335-L4340
- MISChttps://blog.compass-security.com/2012/10/dangerous-sudoers-entries-part-2-insecure-functionality/
- MAILING_LISThttps://lists.debian.org/debian-lts-announce/2023/03/msg00032.html
- MISChttps://security.netapp.com/advisory/ntap-20230505-0009/
- EXPLOIThttp://packetstormsecurity.com/files/174130/systemd-246-Local-Root-Privilege-Escalation.html
Updated 44m ago · 8 sources