Loading vulnerability…
BC Security Empire versions prior to 5.9.3 contain a path traversal vulnerability that allows a remote, unauthenticated attacker to achieve remote code execution. The attacker can exploit this by acting as a normal agent, completing all required cryptographic handshakes, and then uploading payload data with a crafted path that traverses directories, enabling the placement and execution of malicious files on the server.
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 (empire_skywalker.rb) that exploits an arbitrary file upload vulnerability (CVE-2024-6127) in the Empire C2 server (both BC Security Empire and the original PowerShellEmpire). The exploit targets Empire servers running on Linux and allows an attacker to upload a file to the /tmp/ directory and create a cron job in /etc/cron.d/ to execute the uploaded payload, resulting in remote code execution with the permissions of the Empire server process. The module is highly configurable, allowing the attacker to specify the target URI, staging path, and agent profile. The attack is performed over HTTP(S) (default port 8080), and the exploit is weaponized, supporting multiple payload architectures (Python, Linux x86, Linux x64). The module is part of the Metasploit framework and is structured to allow easy payload customization and reliable exploitation. The main endpoints involved are the Empire server's HTTP interface (e.g., /login/process.php), the /tmp/ directory for file upload, and /etc/cron.d/ for persistence via cron.
2 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.