CVE-2020-16846
SaltStack Salt Shell Injection
- Published6 Nov 2020
- Added to CISA KEV3 Nov 2021
- Remediation due3 May 2022
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00029.html
- http://packetstormsecurity.com/files/160039/SaltStack-Salt-REST-API-Arbitrary-Command-Execution.html
- https://github.com/saltstack/salt/releases
- https://lists.debian.org/debian-lts-announce/2020/12/msg00007.html
- https://lists.debian.org/debian-lts-announce/2022/01/msg00000.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TPOGB2F6XUAIGFDTOCQDNB2VIXFXHWMA/
- https://security.gentoo.org/glsa/202011-13
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-16846
- https://www.debian.org/security/2021/dsa-4837
- https://www.saltstack.com/blog/on-november-3-2020-saltstack-publicly-disclosed-three-new-cves/
and 5 more references
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2020-16846 being actively exploited?
Yes. CVE-2020-16846 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 3 Nov 2021.
How severe is CVE-2020-16846?
CVE-2020-16846 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 99.6% probability of exploitation.
Which products are affected by CVE-2020-16846?
Affected products include Saltstack Salt, Debian Linux, Fedoraproject Fedora, Opensuse Leap.
How do I fix CVE-2020-16846?
Upgrade affected software to a fixed version, for example Saltstack Salt 2015.8.13 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2020-16846 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.