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 a salt-master via Salt's ssh_client.

Published: 2017-09-26 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-5200 is rated High Risk (67.7/100): CVSS High severity, with medium exploitation likelihood (EPSS 3.21%). EPSS rose +2.24% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-5200

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.97% 3.21% +2.24%
2 2026-05-31 0.93% 0.97% +0.04%
3 2026-05-30 — 0.93% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-5200

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
9.0 2.0 HIGH
AV:N/AC:L/Au:S/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 8.0 10.0 [email protected]

Weakness enumeration for CVE-2017-5200

GitHub Security Advisory for CVE-2017-5200

GHSA-8r7r-x48r-pf8f · Severity: high · Ecosystem: pip — SaltStack Salt arbitrary command execution in Salt-api via ssh_client

OS Trackers for CVE-2017-5200

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2017-5200
suse medium CVE-2017-5200 severity moderate: SUSE including 36 source package names (beta1:salt-2016.11.4-45.2, beta1:salt-api-2016.11.4-45.2, …), 518 product×package rows across 78 product lines (Container caasp/v4/salt-api, Container caasp/v4/salt-master, … (78 product lines)): Known Not Affected 449, Fixed 69. https://www.suse.com/security/cve/CVE-2017-5200/
ubuntu medium CVE-2017-5200 medium priority: Ubuntu including 1 source packages (salt), 23 status rows across 23 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, precise, questing, trusty, upstream, xenial, yakkety, zesty): not-affected 9, DNE 8, ignored 3, needed 2, released 1. https://ubuntu.com/security/CVE-2017-5200

Affected software / configurations for CVE-2017-5200

Vendor Product Version Raw CPE
saltstack salt <= 2015.8.12 cpe:2.3:a:saltstack:salt:*:*:*:*:*:*:*:*
saltstack salt 2016.3.0 cpe:2.3:a:saltstack:salt:2016.3.0:*:*:*:*:*:*:*
saltstack salt 2016.3.1 cpe:2.3:a:saltstack:salt:2016.3.1:*:*:*:*:*:*:*
saltstack salt 2016.3.2 cpe:2.3:a:saltstack:salt:2016.3.2:*:*:*:*:*:*:*
saltstack salt 2016.3.3 cpe:2.3:a:saltstack:salt:2016.3.3:*:*:*:*:*:*:*
saltstack salt 2016.3.4 cpe:2.3:a:saltstack:salt:2016.3.4:*:*:*:*:*:*:*
saltstack salt 2016.11.0 cpe:2.3:a:saltstack:salt:2016.11.0:*:*:*:*:*:*:*
saltstack salt 2016.11.1 cpe:2.3:a:saltstack:salt:2016.11.1:*:*:*:*:*:*:*
saltstack salt 2016.11.2 cpe:2.3:a:saltstack:salt:2016.11.2:*:*:*:*:*:*:*

References for CVE-2017-5200

cvelogic Threat Intelligence