CVE-2017-11610 is an authenticated remote command execution vulnerability in Supervisor's XML-RPC server. Affected versions include Supervisor before 3.0.1, 3.1.x before 3.1.4, 3.2.x before 3.2.4, and 3.3.x before 3.3.3. The flaw is related to incorrect default permissions and unsafe nested namespace resolution within the supervisord XML-RPC interface. By sending a crafted XML-RPC request that performs nested supervisord namespace lookups, an authenticated user can reach functionality that ultimately invokes operating system command execution. The issue has been observed in exploitation payloads that abuse XML-RPC method resolution to reach Python runtime objects and execute shell commands on the host running supervisord.
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 is a small, focused exploit repo for CVE-2017-11610 in Supervisord. It contains one Python exploit script and one long README walkthrough. The main exploit file, exploit_supervisor.py, uses Python's xmlrpc.client to connect to a target Supervisord XML-RPC endpoint at /RPC2, then abuses recursive namespace traversal via the method path supervisor.supervisord.options.warnings.linecache.os.system to invoke os.system remotely with an attacker-supplied command. This provides remote command execution over the network against vulnerable, exposed Supervisord instances. Repository structure is minimal: README.md documents reconnaissance, validation of the exposed web UI and XML-RPC API, example target observations, impact, and remediation; exploit_supervisor.py is the operational entry point. The script accepts two command-line arguments: target_url and command. It prints status messages, builds a ServerProxy to <target_url>/RPC2, resolves the dangerous method path, and executes the provided command, reporting the returned exit code. The exploit capability is straightforward but real: arbitrary shell command execution in the privileges of the supervisord process, likely a low-privileged service account unless misconfigured. It is not a detection-only script and does not include post-exploitation automation, persistence, or payload staging, so OPERATIONAL is the best maturity fit rather than WEAPONIZED. The attack vector is network/web because exploitation occurs remotely over HTTP/XML-RPC on the Supervisord management port, typically 9001. Fingerprintable observables include the /RPC2 endpoint, the Supervisord web interface on port 9001, the recursive XML-RPC method path used for exploitation, and example targets such as http://192.168.3.137:9001 and http://127.0.0.1:9001. The README also references insecure binding to 0.0.0.0:9001 and example filesystem artifacts such as /tmp/nyx_success. Overall, this repo's purpose is to demonstrate and exploit unauthenticated remote code execution in vulnerable Supervisord deployments exposed via inet_http_server.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remote code execution flaw in Supervisor XML-RPC server that the content says Sysrv incorporated for spreading.
A remote code execution vulnerability in Supervisord's XML-RPC interface that the worm scans for and exploits to propagate and deploy the miner.
An unauthenticated command injection / RCE condition in Supervisord’s XML-RPC interface, scanned here via crafted XML-RPC method calls that invoke OS command execution and confirm via OAST (e.g., nslookup).
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.