Loading vulnerability…
In HashiCorp Consul Enterprise versions prior to 1.8.17, 1.9.11, and 1.10.4, an incorrect access control vulnerability exists where an ACL token with default operator:write permissions in one namespace can be used to escalate privileges in a different namespace. This allows an attacker with access to a token in one namespace to perform unauthorized actions in another namespace, violating intended access boundaries.
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 Python exploit script (CVE-2021-41805.py) targeting HashiCorp Consul Enterprise servers vulnerable to CVE-2021-41805. The exploit abuses an ACL token with operator:write permissions to register a malicious service via the Consul HTTP API endpoint (/v1/agent/service/register), injecting a health check that executes a reverse shell payload. The attacker must provide the target's IP and port, their own listener IP and port, and optionally an ACL token and SSL flag. The script sends a crafted PUT request to the Consul API, causing the target to connect back to the attacker's listener with a bash reverse shell. The repository also includes a README with usage instructions and a LICENSE file. The exploit is operational and provides a working reverse shell if the target is vulnerable and properly configured.
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.