CVE-2020-25592 affects SaltStack Salt through version 3002. In salt-netapi, eauth credentials and tokens are improperly validated, allowing an attacker to bypass authentication checks and invoke Salt SSH functionality. The issue is rooted in insufficient verification of externally supplied authentication material within the netapi interface, enabling unauthorized access to privileged orchestration capabilities exposed through Salt SSH.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/linux/http/saltstack_salt_api_cmd_exec.rb) that exploits two vulnerabilities (CVE-2020-16846 and CVE-2020-25592) in SaltStack Salt's REST API (salt-api). The exploit leverages an authentication bypass and command injection to execute arbitrary commands as root on vulnerable SaltStack Salt installations. The module supports both direct command execution (Unix Command target) and staged payload delivery (Linux Dropper target), allowing for reverse shells or Meterpreter sessions. The main attack vector is network-based, targeting the /run HTTP endpoint of the salt-api service, typically running on port 8000 with SSL enabled. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The repository is structured as a single Ruby file, following Metasploit conventions, and is intended for use within the Metasploit framework.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.