CVE-2020-16846

Known Exploited Public Exploit

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.

Category

9.8
CVSS
Severity: Critical
CVSS 3.1 •
CVSS 2.0 •
EPSS 94.39% Top 5%
KEV Since 
Vendor Advisory fedoraproject.org Vendor Advisory opensuse.org Vendor Advisory gentoo.org Vendor Advisory debian.org Vendor Advisory saltstack.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/saltstack/salt/releases release notes
https://www.saltstack.com/blog/on-november-3-2020-saltstack-publicly-disclosed-three-new-cves/ vendor advisory broken link
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TPOGB2F6XUAIGFDTOCQDNB2VIXFXHWMA/ release notes vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00029.html vendor advisory mailing list third party advisory
https://security.gentoo.org/glsa/202011-13 third party advisory vendor advisory
http://packetstormsecurity.com/files/160039/SaltStack-Salt-REST-API-Arbitrary-Command-Execution.html third party advisory vdb entry exploit
https://www.zerodayinitiative.com/advisories/ZDI-20-1381/ third party advisory vdb entry
https://www.zerodayinitiative.com/advisories/ZDI-20-1383/ third party advisory vdb entry
https://www.zerodayinitiative.com/advisories/ZDI-20-1380/ third party advisory vdb entry
https://www.zerodayinitiative.com/advisories/ZDI-20-1379/ third party advisory vdb entry
https://www.zerodayinitiative.com/advisories/ZDI-20-1382/ third party advisory vdb entry
https://lists.debian.org/debian-lts-announce/2020/12/msg00007.html third party advisory mailing list
https://www.debian.org/security/2021/dsa-4837 vendor advisory mailing list third party advisory
https://lists.debian.org/debian-lts-announce/2022/01/msg00000.html third party advisory mailing list

Frequently Asked Questions

What is the severity of CVE-2020-16846?
CVE-2020-16846 has been scored as a critical severity vulnerability.
How to fix CVE-2020-16846?
To fix CVE-2020-16846, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-16846 being actively exploited in the wild?
It is confirmed that CVE-2020-16846 is actively exploited. Be extra cautious if you are using vulnerable components. According to its EPSS score, there is a ~94% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.