A buffer overflow vulnerability exists in McAfee ePolicy Orchestrator versions prior to 3.5.0.720 and ProtectionPilot versions prior to 1.1.1.126. The flaw is triggered by a specially crafted request to the /spipe/pkg/ endpoint with an overly long source header, allowing remote attackers to overflow a buffer and potentially execute arbitrary code on the affected system.
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 targeting a stack buffer overflow vulnerability in the McAfee ePolicy Orchestrator (ePO) HTTP server (NAISERV.exe), affecting versions 2.5.1 (SP1) through 3.5.0 and ProtectionPilot 1.1.0. The exploit works by sending a specially crafted HTTP request to TCP port 81, with an overlong 'Source' header that triggers the overflow. The module uses the egghunter technique to deliver a customizable payload (up to 1000 bytes, avoiding specific bad characters), which can result in remote code execution as SYSTEM. The module includes a check method to verify the presence of the vulnerable service by requesting '/SITEINFO.INI' and looking for a 'Spipe/1.0' banner. The main exploit is delivered via a GET request to '/spipe/pkg'. The code is written in Ruby and is structured as a standard Metasploit exploit module, making it easy to use within the Metasploit framework.
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.