A command injection vulnerability exists in Acemanager in ALEOS before version 4.16, where a user with valid credentials can manipulate the IP logging operation to execute arbitrary shell commands on the device. This allows attackers to run commands with the privileges of the Acemanager process.
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 standalone Python proof-of-concept exploit for CVE-2022-46649. It contains three files: an MIT LICENSE, a README describing the vulnerability and usage, and a single executable script, exploit.py, which is the main entry point. The exploit is not part of a larger framework. The script performs two stages. First, it authenticates to the target over HTTPS by POSTing XML credentials to /xml/Connect.xml using requests.Session(), which preserves cookies for the authenticated session. Second, it sends a POST request to /admin/tools/iplogging.cgi with a crafted tcpdumpParams value: '-i eth0 -G 1 -z<command>'. The attacker-controlled command is appended to the tcpdump -z option, enabling authenticated OS command injection and remote command execution. Operationally, the exploit requires a reachable HTTPS management interface and valid credentials. SSL verification is explicitly disabled, making it tolerant of self-signed certificates. The payload is simple but functional: it accepts an arbitrary command from the command line and submits it directly to the vulnerable endpoint. There is no output capture, shell staging, persistence, or post-exploitation automation; it only reports whether the HTTP request succeeded. This makes it an operational authenticated RCE PoC rather than a detection script or fake exploit.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.