CVE-2017-5200: 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…
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.2% (FIRST EPSS); higher than 88.7% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: salt (Alpine:v3.5) 2016.11.2-r0; salt (PyPI) 2016.11.2, 2016.3.5, 2015.8.13; salt (SUSE:Linux Enterprise Server 11 SP3-CLIENT-TOOLS) 2016.11.4-42.2.
Low priority for now. Upgrade to salt (Alpine:v3.5) 2016.11.2-r0; salt (PyPI) 2016.11.2, 2016.3.5, 2015.8.13; salt (SUSE:Linux Enterprise Server 11 SP3-CLIENT-TOOLS) 2016.11.4-42.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 26, 2017
- Updated
- Jun 16, 2026
- EPSS
- 3.2% · 88th percentile
- CWE
- —
Report tools
Action score
36
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| saltstack | salt | cpe:2.3:a:saltstack:salt |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- saltstack saltup to 2015.8.12 inclusive
- saltstack salt2016.11.0
- saltstack salt2016.11.1
- saltstack salt2016.11.2
- saltstack salt2016.3.0
- saltstack salt2016.3.1
- saltstack salt2016.3.2
- saltstack salt2016.3.3
- saltstack salt2016.3.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.5 | salt | before 2016.11.2-r0 | 2016.11.2-r0 |
| PyPI | salt | from 2016.11 · before 2016.11.2 | 2016.11.2 |
| PyPI | salt | from 2016.11.0 · before 2016.11.2 | 2016.11.2 |
| PyPI | salt | from 2016.3 · before 2016.3.5 | 2016.3.5 |
| PyPI | salt | from 2016.3.0 · before 2016.3.5 | 2016.3.5 |
| PyPI | salt | before 2015.8.13 | 2015.8.13 |
| SUSE:Linux Enterprise Server 11 SP3-CLIENT-TOOLS | salt | before 2016.11.4-42.2 | 2016.11.4-42.2 |
| SUSE:Manager Client Tools 12 | salt | before 2016.11.4-45.2 | 2016.11.4-45.2 |
Same product
saltstack: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-16846An issue was discovered in SaltStack Salt through 3002.KEV99Now
- CVE-2020-11651An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2.KEV98Now
- CVE-2020-11652An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2.KEV82Now
Published before and after this one in the same product
- ← EarlierCVE-2015-4017Aug 25, 2017 · Salt before 2014.7.6 does not verify certificates when connecting via the aliyun, proxmox, and splunk modules.30Monitor
- ← EarlierCVE-2017-5192Sep 26, 2017 · When using the local_batch client from salt-api in SaltStack Salt before 2015.8.13, 2016.3.x before 2016.3.5, and 2016.11.x before…36Monitor
- Later →CVE-2017-14695Oct 24, 2017 · Directory traversal vulnerability in minion id validation in SaltStack Salt before 2016.3.8, 2016.11.x before 2016.11.8, and 2017.7.x…40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:salt | 2016.11.2-r0 · Alpine:v3.5 | Package registry (OSV) |
| PyPI:salt | 2015.8.13 | Package registry (OSV) |
| PyPI:salt | 2016.11.2 | Package registry (OSV) |
| PyPI:salt | 2016.3.5 | Package registry (OSV) |
| suse:salt | 2016.11.4-42.2 · SUSE:Linux Enterprise Server 11 SP3-CLIENT-TOOLS | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.