Information Disclosure in salt (CVE-2017-8109)
Summary
Vulnerability in salt (CVE-2017-8109). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2016.11.4 or later.
Original description
The description as published by the source.
The salt-ssh minion code in SaltStack Salt 2016.11 before 2016.11.4 copied over configuration from the Salt Master without adjusting permissions, which might leak credentials to local attackers on configured minions (clients).
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-8109 has been found in salt.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade salt to 2016.11.4 or later.
If unsure, ask your IT team or search "salt CVE-2017-8109" on the vendor's site.
CVE-2017-8109 (salt) — CWE-200 / CVSS v3 7.8
Attack vector: local / no user interaction
Patched: 2016.11.4 — 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.
Information disclosure (CWE-200) exists in salt.
Check the vendor advisory for the affected versions of salt.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 2016.11.4.
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 2016.11.4ステージング環境で 2016.11.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory securityfocus.com
- advisory github.com
- patch bugzilla.suse.com
- patch docs.saltstack.com
- patch github.com
- patch github.com
- patch github.com