CVE-2017-5200
No exploitation reported by the sources we read.
- Published2017-09-26
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2017-09-2614:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-5200?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-5200?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2015.8 | ≤ 2015.8.12 | no fix published | NVD |
| 2016.3 | = 2016.3.0 | no fix published | NVD |
| 2016.3 | = 2016.3.1 | no fix published | NVD |
| 2016.3 | = 2016.3.2 | no fix published | NVD |
| 2016.3 | = 2016.3.3 | no fix published | NVD |
| 2016.3 | = 2016.3.4 | no fix published | NVD |
| 2016.11 | = 2016.11.0 | no fix published | NVD |
| 2016.11 | = 2016.11.1 | no fix published | NVD |
| 2016.11 | = 2016.11.2 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2016.11 | ≥ 2016.11.0, < 2016.11.2 | 2016.11.2 | OSV |
| 2016.11 | ≥ 2016.11, < 2016.11.2 | 2016.11.2 | OSV |
| 2016.3 | ≥ 2016.3.0, < 2016.3.5 | 2016.3.5 | OSV |
| 2016.3 | ≥ 2016.3, < 2016.3.5 | 2016.3.5 | OSV |
| 2015.8 | < 2015.8.13 | 2015.8.13 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- docs.saltstack.comRelease Notes · Vendor Advisory
- docs.saltstack.comRelease Notes · Vendor Advisory
- docs.saltstack.comRelease Notes · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.08.8read 2026-10-23
- NVDCVSS 2.09read 2026-10-23
- FIRST EPSSEPSS score3.2 %2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2017-09-26
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-5200?
Is CVE-2017-5200 actively exploited?
What is the CVSS score for CVE-2017-5200?
Running salt? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.