Root file takeover via unsafe post-install chown
Published Jan 15, 2024 · Updated Jun 20, 2025
Incorrect ownership assignment in the Gentoo Slurm ebuild through 22.05.3 allows local users with slurm account access to take over root-owned files. The ebuild's pkg_postinst function runs chown against files in the live root filesystem and assigns their ownership to the slurm user without a necessary ownership change. Exploitation requires local slurm-account access and can transfer control of root-owned files, enabling privilege escalation through later file modification.
Summary
What happened
Incorrect ownership assignment in the Gentoo Slurm ebuild through 22.05.3 allows local users with slurm account access to take over root-owned files. The ebuild's pkg_postinst function runs chown against files in the live root filesystem and assigns their ownership to the slurm user without a necessary ownership change. Exploitation requires local slurm-account access and can transfer control of root-owned files, enabling privilege escalation through later file modification.
The record
- CVE
- CVE-2020-36770
- Published
- Jan 15, 2024
- Updated
- Jun 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-732, T1222.002, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 15, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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