← Back
CVE-2020-11651
CISA KEV
high
[KEV] Vulnerability in Saltstack salt (CVE-2020-11651)
Summary
vulnerability in Saltstack salt (CVE-2020-11651). Risk of unauthorized operations or information disclosure. Listed in CISA KEV — actively exploited. Mitigation: upgrade to `2019.2.4, 3000.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2020-11651** has been found in Saltstack salt.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
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-11651" on the vendor's site.
CVE-2020-11651 (Saltstack salt) —
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.
❓ What is the problem
**A vulnerability** (unclassified) exists in Saltstack salt.
📍 Affected scope
Saltstack salt — .
🔥 Severity
Severity: High. Risk of unauthorized operations or information disclosure **Listed in CISA KEV** — actively exploited in the wild, treat as top priority.
🔧 How to fix
Update to **2019.2.4, 3000.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
4Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。Step 3 で兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
6Apply patch patch
Upgrade salt to 2019.2.4, 3000.2ステージング環境で 2019.2.4, 3000.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
salt
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2019.2.4"},{"introduced":"3000"},{"fixed":"3000.2"}]}]
References
- advisory NVD
- advisory https://www.debian.org/security/2020/dsa-4676
- advisory http://www.vmware.com/security/advisories/VMSA-2020-0009.html
- advisory https://github.com/advisories/GHSA-pjhf-vpx3-33r3
- web https://docs.saltstack.com/en/latest/topics/releases/2019.2.4.html
- web https://github.com/saltstack/salt/blob/v3000.2_docs/doc/topics/releases/3000.2.rst
- web http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00047.html
- web http://packetstormsecurity.com/files/157560/Saltstack-3000.1-Remote-Code-Execution.html
- web http://packetstormsecurity.com/files/157678/SaltStack-Salt-Master-Minion-Unauthenticated-Remote-Code-Execution.html
- web https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-salt-2vx545AG
- web https://lists.debian.org/debian-lts-announce/2020/05/msg00027.html
- web http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00070.html
- web https://usn.ubuntu.com/4459-1/