Xplico versions before 1.2.1 improperly handle shell metacharacters in uploaded PCAP filenames. An attacker can supply a crafted filename that is interpreted by a shell during processing, resulting in arbitrary command execution. Although the issue is described as affecting authenticated remote users, the product's user-registration feature permits exploitation without prior authentication.
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 (1 hidden).
This repository contains a single Metasploit module (modules/exploits/linux/http/xplico_exec.rb) targeting a remote code execution vulnerability (CVE-2017-16666) in Xplico, a network forensics analysis tool. The exploit leverages a command injection flaw in the PCAP file upload and processing functionality. The module automates the process of registering a new user (via /users/register), logging in, creating a new case and solution, and uploading a specially crafted PCAP file to trigger the vulnerability. The exploit achieves code execution as root by injecting commands into the checksum calculation routine. The module is written in Ruby and is structured according to Metasploit conventions, using the HttpClient mixin to interact with the target's web interface (default port 9876). The main attack vector is network-based, exploiting the HTTP interface of Xplico. The module is operational and provides a command execution payload, but is not weaponized for mass exploitation.
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.