[KEV] Path Traversal in Saltstack salt (CVE-2020-11652)
Summary
Path traversal in Saltstack salt (CVE-2020-11652). Confidential information can be exposed externally. Listed in CISA KEV — actively exploited. Mitigation: upgrade to 2019.2.4, 3000.2 or later.
Original description
The description as published by the source.
An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2. The salt-master process ClearFuncs class allows access to some methods that improperly sanitize paths. These methods allow arbitrary directory access to authenticated users.
Source: CISA Known Exploited Vulnerabilities NVD GitHub Advisory CISA KEV
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-2020-11652 has been found in Saltstack salt.
Confidential information can be exposed externally.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: upgrade Saltstack salt to 2019.2.4, 3000.2 or later.
If unsure, ask your IT team or search "Saltstack salt CVE-2020-11652" on the vendor's site.
CVE-2020-11652 (Saltstack salt) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Patched: 2019.2.4, 3000.2 — apply immediately
Listed in CISA KEV — actively exploited, treat as top priority.
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.
Path traversal (CWE-22) exists in Saltstack salt.
Check the vendor advisory for the affected versions of Saltstack salt.
Severity: High. Confidential information can be exposed externally. Listed in CISA KEV — actively exploited in the wild, treat as top priority.
Update to 2019.2.4, 3000.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 し、稼働しているサービス・バージョンを把握する。 -
2Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
3Apply patch patch
Upgrade Saltstack salt to 2019.2.4, 3000.2ステージング環境で 2019.2.4, 3000.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory NVD
- advisory docs.saltstack.com
- advisory github.com
- advisory lists.opensuse.org
- advisory packetstormsecurity.com
- advisory debian.org
- advisory vmware.com
- advisory tools.cisco.com
- advisory lists.debian.org
- advisory support.blackberry.com
- advisory lists.opensuse.org
- advisory usn.ubuntu.com
- advisory github.com
- report packetstormsecurity.com
- web cisa.gov