CVE-2017-5200 json
SaltStack Salt arbitrary command execution in Salt-api via ssh_client
published 2017-09-26 9 y ago modified 2026-06-17 4 mo ago also GHSA-8r7r-x48r-pf8f , PYSEC-2017-39 , EUVD-2017-0123
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.3%
- EPSS 3.3% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
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 ssh_client.
Patch / fix
- pypi salt 2015.8.13, 2016.3.5, 2016.11.2
- salt SLE Point of Sale 12 SP2, SLE Module for Advanced Systems Management 12, Manager Server 3.0 +4 more 2016.11.4-45.2
- salt SLES 11 SP4-CLIENT-TOOLS, SLES 11 SP3-CLIENT-TOOLS 2016.11.4-42.2
suse advisories SUSE-SU-2017:1582-1SUSE-SU-2017:1581-1
- salt Alpine 3.5 2016.11.2-r0
alpine advisories ALPINE-CVE-2017-5200
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-5200 updated cvss 7.5
salt: Salt-api allows arbitrary command execution on a salt-master via Salt's ssh_client
-
Red Hat Ceph Storage 1.3 salt Red Hat Ceph Storage 2 salt, salt-minion Red Hat Storage Console 2 saltnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.29% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
| GitHub | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | salt | <2015.8.13 >=2016.3.0, <2016.3.5 >=2016.11.0, <2016.11.2 >=2016.3, <2016.3.5 >=2016.11, <2016.11.2 |
2015.8.13 2016.3.5 2016.11.2 |
References
-
docs.saltstack.com
/en/2016.3/topics/releases/2015.8.13.html
web, release-notes, vendor-advisory
-
docs.saltstack.com
/en/2016.3/topics/releases/2016.3.5.html
web, release-notes, vendor-advisory
-
docs.saltstack.com
/en/latest/topics/releases/2016.11.2.html
web, release-notes, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-5200
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/salt/PYSEC-2017-39.yaml
web
-
github.com
/saltstack/salt
package
-
github.com
/advisories/GHSA-8r7r-x48r-pf8f
advisory
Sources
- CVE List CVE-2017-5200
- GitHub Advisory GHSA-8r7r-x48r-pf8f
- NVD CVE-2017-5200
- OSV PYSEC-2017-39
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.