Patchfirst
CVE-2020-16846 KEVPublic exploit Critical · 9.8 EPSS 99.6%

SaltStack Salt Shell Injection Vulnerability

SaltStack · Salt

Summary

A shell injection flaw exists in SaltStack Salt through version 3002, in its Salt API component when the SSH client is enabled. An unauthenticated remote attacker who can reach the API can send crafted web requests that inject operating system commands, with no user interaction required.

Official description · NVD

An issue was discovered in SaltStack Salt through 3002. Sending crafted web requests to the Salt API, with the SSH client enabled, can result in shell injection.

Breakdown
69.8 / 100
Exploited
Yes, in CISA KEV
Reports
0
Tactics
2/15

How an attack unfolds

Based on mappings. Select a step to see the evidence.
  1. How attackers get in

  2. What they do

First seen exploited 6 months after disclosure. Public exploit code (Metasploit) was available 3 days before disclosure.

  1. Public exploit codeMetasploit3 days before
  2. Disclosedday 0
  3. First seen exploitedVulnCheck KEV evidence+6 mo
  4. Added to CISA KEVEU database agrees+12 mo

CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.

7 fixes in salt over 14 months. The latest fix listed for salt is 3002.2.

Fixes in saltPyPI package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 2019.2.3CVE-2019-1736117 Jan 2020
  2. 3000.2CVE-2020-1165130 Apr 2020KEV
  3. 3000.2CVE-2020-1165230 Apr 2020KEV
  4. 3002.1CVE-2020-168466 Nov 2020KEV
  5. 3002.1CVE-2020-174906 Nov 2020
  6. 3002.1CVE-2020-255926 Nov 2020
  7. 3002.2CVE-2021-253153 Mar 2021Latest listed

techniques

2 , grouped by in kill-chain order, 2 cited passages 2

Initial AccessTA0001

Exploit Public-Facing Application T1190 Medium
AI mapping from the description · how it is exploited

Unauthenticated crafted requests to public-facing API

Sending crafted web requests to the Salt API
From the official description (NVD) Original (opens in a new tab) ↗

ExecutionTA0002

Command and Scripting Interpreter T1059 Medium
AI mapping from the description · primary impact

Shell injection enables arbitrary command execution

can result in shell injection
From the official description (NVD) Original (opens in a new tab) ↗

Detection

0 rules for this CVE · 244 general rules for its techniques

Rules for this CVE

0 that reference CVE-2020-16846 directly.

CVE-specific rules are not available in this build. Search SigmaHQ ↗

Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: salt.

Upgrade to 3002.5 or later

Fixes this CVE and 4 other known vulnerabilities in this package (CVE-2020-25592, CVE-2021-25281, +2).

pippip install "salt>=3002.5"

First fixed in 3002.1 for CVE-2020-16846.

Affected versions, by release line

If you runUpgrade to
3002 up to 3002.13002.5first fix for this CVE: 3002.1
3001 up to 3001.23001.5first fix for this CVE: 3001.2
3000.0 up to 3000.43000.7first fix for this CVE: 3000.4
3000 up to 3000.3

Still affected on this line by CVE-2020-25592 (fixed in 3000.5, a newer line); CVE-2021-25281 (fixed in 3000.6, a newer line); CVE-2021-25282 (fixed in 3000.6, a newer line); CVE-2021-3197 (fixed in 3000.6, a newer line).

3000.3
2019.2.0 up to 2019.2.62019.2.8first fix for this CVE: 2019.2.6
2019.2.0 up to 2019.2.5

Still affected on this line by CVE-2020-25592 (fixed in 2019.2.7, a newer line); CVE-2021-25281 (fixed in 2019.2.8, a newer line); CVE-2021-25282 (fixed in 2019.2.8, a newer line); CVE-2021-3197 (fixed in 2019.2.8, a newer line).

2019.2.5
2018.3.0rc1 up to 2018.3.5

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line).

2019.2.0rc1first fix for this CVE: 2018.3.5
2018.2.0 up to 2018.3.5

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line); CVE-2021-25281 (fixed in 2019.2.0rc1, a newer line); CVE-2021-25282 (fixed in 2019.2.0rc1, a newer line); CVE-2021-3197 (fixed in 2019.2.0rc1, a newer line).

2018.3.5
2017.7.5 up to 2017.7.8

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line).

2017.7.8
2017.7.0 up to 2017.7.4

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line); CVE-2020-25592 (fixed in 2017.7.8, a newer line); CVE-2021-25281 (fixed in 2017.7.8, a newer line); CVE-2021-25282 (fixed in 2017.7.8, a newer line); CVE-2021-3197 (fixed in 2017.7.8, a newer line).

2017.7.4
2017.5.0 up to 2017.7.8

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line).

2017.7.8
2016.11.7 up to 2016.11.10

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line).

2016.11.10
2016.11.4 up to 2016.11.6

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line); CVE-2020-25592 (fixed in 2016.11.10, a newer line).

2016.11.6
2016.11.0 up to 2016.11.10

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line).

2016.11.10
2016.11.0 up to 2016.11.3

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line); CVE-2020-25592 (fixed in 2016.11.10, a newer line); CVE-2021-25281 (fixed in 2016.11.5, a newer line); CVE-2021-25282 (fixed in 2016.11.5, a newer line); CVE-2021-3197 (fixed in 2016.11.5, a newer line).

2016.11.3
2016.3.7 up to 2016.3.8

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line); CVE-2021-25281 (fixed in 2016.11.5, a newer line); CVE-2021-25282 (fixed in 2016.11.5, a newer line); CVE-2021-3197 (fixed in 2016.11.5, a newer line).

2016.3.8
2016.3.5 up to 2016.3.6

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line); CVE-2020-25592 (fixed in 2016.3.8, a newer line); CVE-2021-25281 (fixed in 2016.11.5, a newer line); CVE-2021-25282 (fixed in 2016.11.5, a newer line); CVE-2021-3197 (fixed in 2016.11.5, a newer line).

2016.3.6
2016.3.0 up to 2016.3.8

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line); CVE-2021-25281 (fixed in 2016.11.5, a newer line); CVE-2021-25282 (fixed in 2016.11.5, a newer line); CVE-2021-3197 (fixed in 2016.11.5, a newer line).

2016.3.8
2016.3.0 up to 2016.3.4

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line); CVE-2020-25592 (fixed in 2016.3.8, a newer line); CVE-2021-25281 (fixed in 2016.11.5, a newer line); CVE-2021-25282 (fixed in 2016.11.5, a newer line); CVE-2021-3197 (fixed in 2016.11.5, a newer line).

2016.3.4
All versions before 2015.8.13

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line).

2015.8.13
All versions before 2015.8.10

Still affected on this line by CVE-2020-11651 (fixed in 2019.2.4, a newer line); CVE-2020-11652 (fixed in 2019.2.4, a newer line).

2015.8.13first fix for this CVE: 2015.8.10

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

Also mentioned in 50 community threat pulses (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

References

15 links, grouped by NVD tag (14 duplicates merged)
↑ ↓ chooseEnter openEsc close