CVE-2017-5200: Critical severity saltstack vulnerability
Published Sep 26, 2017
·Updated
Salt-api in SaltStack Salt before 2015.8.13, 2016.3.x before 2016.3.5, and 2016.11.x before 2016.11.2 allows arbitrary command execution on a salt-master via Salt's sshclient.
Affected Software
12 affected componentsFixes available
pip/salt>=2016.11.0<2016.11.2
2016.11.2
pip/salt>=2016.3.0<2016.3.5
2016.3.5
pip/salt<2015.8.13
2015.8.13
SaltStack Salt<=2015.8.12
SaltStack Salt=2016.3.0
SaltStack Salt=2016.3.1
SaltStack Salt=2016.3.2
SaltStack Salt=2016.3.3
SaltStack Salt=2016.3.4
SaltStack Salt=2016.11.0
SaltStack Salt=2016.11.1
SaltStack Salt=2016.11.2
Event History
Sep 26, 2017
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
May 13, 2022
Advisory Published
via GitHub·01:46 AM
Frequently Asked Questions
1
What is the severity of CVE-2017-5200?
CVE-2017-5200 is considered a high severity vulnerability due to its potential for arbitrary command execution on a salt-master.
2
How do I fix CVE-2017-5200?
To fix CVE-2017-5200, update SaltStack Salt to version 2015.8.13, 2016.3.5, or 2016.11.2.
3
What versions of SaltStack Salt are affected by CVE-2017-5200?
CVE-2017-5200 affects SaltStack Salt versions before 2015.8.13, 2016.3.x before 2016.3.5, and 2016.11.x before 2016.11.2.
4
What type of vulnerability is CVE-2017-5200?
CVE-2017-5200 is categorized as a remote command execution vulnerability.
5
Who is impacted by CVE-2017-5200?
Organizations using affected versions of SaltStack Salt for configuration management and automation are impacted by CVE-2017-5200.