First published: Tue Jan 12 2021(Updated: )
An issue was discovered in ClusterLabs crmsh through 4.2.1. Local attackers able to call "crm history" (when "crm" is run) were able to execute commands via shell code injection to the crm history commandline, potentially allowing escalation of privileges.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/crmsh | <=4.2.1 | |
ClusterLabs crmsh | <=4.2.1 | |
Debian Debian Linux | =9.0 | |
ubuntu/crmsh | <4.2.0-2ubuntu1.1 | 4.2.0-2ubuntu1.1 |
ubuntu/crmsh | <4.2.1-2 | 4.2.1-2 |
ubuntu/crmsh | <4.2.1-2 | 4.2.1-2 |
debian/crmsh | 4.0.0~git20190108.3d56538-3+deb10u1 4.2.1-2 4.4.1-1 4.6.0-2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-35459 is a vulnerability in ClusterLabs crmsh through version 4.2.1 that allows local attackers to execute commands via shell code injection to the crm history commandline.
The severity of CVE-2020-35459 is high with a CVSS score of 7.8.
CVE-2020-35459 affects ClusterLabs crmsh versions up to and including 4.2.1.
Yes, upgrading to a version of ClusterLabs crmsh that is not affected, such as version 4.2.2 or later, can fix CVE-2020-35459.
Yes, you can find more information about CVE-2020-35459 at the following references: [NVD](https://nvd.nist.gov/vuln/detail/CVE-2020-35459), [Bugzilla](https://bugzilla.suse.com/show_bug.cgi?id=1179999), [GitHub](https://github.com/ClusterLabs/crmsh/blob/a403aa15f3ea575adfe5e43bf2a31c9f9094fcda/crmsh/history.py#L476).