Root command execution via unfiltered session directory
Published Jan 12, 2021 · Updated Aug 4, 2024
Command injection in ClusterLabs crmsh 4.2.1 and earlier allows local users to execute commands as root through crm history session creation. The history session-create path interpolates an unfiltered session directory into a shell command that invokes mkdir -p. When crm history is called through the setuid-root hawk_invoke helper, its whitelist admits the subcommand and hauser or vagrant input reaches that shell.
Summary
What happened
Command injection in ClusterLabs crmsh 4.2.1 and earlier allows local users to execute commands as root through crm history session creation. The history session-create path interpolates an unfiltered session directory into a shell command that invokes mkdir -p. When crm history is called through the setuid-root hawk_invoke helper, its whitelist admits the subcommand and hauser or vagrant input reaches that shell.
The record
- CVE
- CVE-2020-35459
- Published
- Jan 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-269, CWE-78, T1068, T1059.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 12, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- oss-security crmsh shell-injection disclosureproof of concept · unverified
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