Root escalation via privileged post-install script
Published Sep 7, 2022 · Updated Sep 17, 2024
Incorrect default permissions in openSUSE Factory slurm before 22.05.2-3.3 allow local users controlling the slurm account to gain root. The slurm-testsuite package's %post script performs root-privileged operations from a directory owned by the slurm user, allowing attacker-controlled directory content to redirect those operations. Exploitation requires local control of the slurm account and package installation or update to invoke the script, after which attacker-controlled actions run with root privileges.
Summary
What happened
Incorrect default permissions in openSUSE Factory slurm before 22.05.2-3.3 allow local users controlling the slurm account to gain root. The slurm-testsuite package's %post script performs root-privileged operations from a directory owned by the slurm user, allowing attacker-controlled directory content to redirect those operations. Exploitation requires local control of the slurm account and package installation or update to invoke the script, after which attacker-controlled actions run with root privileges.
The record
- CVE
- CVE-2022-31251
- Published
- Sep 7, 2022
- Updated
- Sep 17, 2024
- Vendor
- SUSE
- Product
- openSUSE Factory
- Classifications
- CWE-276, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 7, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=slurm <22.05.2-3.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo