CVE-2021-25282 is a directory traversal vulnerability in SaltStack Salt affecting versions before 3002.5. The issue is in the salt.wheel.pillar_roots.write method, which does not adequately restrict file path handling, allowing traversal outside the intended pillar roots directory. An attacker able to invoke this method can supply crafted path input to cause files to be written to unintended locations on the Salt master filesystem.
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_wheel_async_rce.rb) that exploits two vulnerabilities (CVE-2021-25281 and CVE-2021-25282) in SaltStack Salt's REST API. The exploit leverages an authentication bypass and directory traversal to drop a malicious Python script into the Salt master's extension modules directory. The Salt master's maintenance process will execute this script as root, allowing for remote code execution. The module supports both direct command execution and staged payloads (such as Meterpreter reverse shells), and is weaponized for operational use within the Metasploit framework. The main attack vector is network-based, targeting the Salt API (typically over HTTPS on port 8000). The module is configurable for the extension modules directory and base URI, and includes cleanup routines to remove traces of the exploit. The repository is structured as a single Ruby file, following standard Metasploit module conventions.
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.