Vulnerability in salt (CVE-2017-5200)
Summary
Vulnerability in salt (CVE-2017-5200). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2015.8.13, 2016.3.5, 2016.11.2 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2017-5200 has been found in salt.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade salt to 2015.8.13, 2016.3.5, 2016.11.2 or later.
If unsure, ask your IT team or search "salt CVE-2017-5200" on the vendor's site.
CVE-2017-5200 (salt) — CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 2015.8.13, 2016.3.5, 2016.11.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in salt.
Check the vendor advisory for the affected versions of salt.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2015.8.13, 2016.3.5, 2016.11.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'salt' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'salt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
saltを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade salt to 2015.8.13, 2016.3.5, 2016.11.2ステージング環境で 2015.8.13, 2016.3.5, 2016.11.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- web docs.saltstack.com
- web docs.saltstack.com
- web docs.saltstack.com