Local root escalation via unsanitized umask
Published May 27, 2021 · Updated Aug 3, 2024
Incorrect permission assignment in pleaser before 0.4.0 allows local users to gain root privileges through a writable token directory. The setuid-root process passes the caller-controlled umask to create_dir_all when creating /var/run/pleaser/token, allowing world-writable permissions. Exploitation requires permission to run at least one configured command and enables forged authentication tokens and writes to root-owned files.
Summary
What happened
Incorrect permission assignment in pleaser before 0.4.0 allows local users to gain root privileges through a writable token directory. The setuid-root process passes the caller-controlled umask to create_dir_all when creating /var/run/pleaser/token, allowing world-writable permissions. Exploitation requires permission to run at least one configured command and enables forged authentication tokens and writes to root-owned files.
The record
- CVE
- CVE-2021-31155
- Published
- May 27, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-732, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
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
- Token-directory local privilege-escalation procedurefunctional · demonstrated
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