CVE-2023-26604
systemd before 247 does not adequately block local privilege escalation for some Sudo configurations, e.g., plausible sudoers files in which the "systemctl status" com…
Published Mar 3, 2023 · updated Oct 14, 2026 · debian debian linux
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.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Mar 3, 2023 · NIST NVD
Detected
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 execute
Oct 14, 2026 · NIST NVD
Updated
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 execute
Affected
- cpe debian/debian linux10.0
- cpe systemd project/systemdversion unspecified
Sources
- CVE.orgVulnerability recordCVE-2023-26604
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2023-26604
30-day exploitation probability 1.1%
first.org - NIST NVDVulnerability recordCVE-2023-26604
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
nvd.nist.gov - Packet Storm SecurityCited referencehttp://packetstormsecurity.com/files/174130/systemd-246-Local-Root-Privilege-Escalation.html
Packet Storm link already published on the finding.
packetstormsecurity.com