A stack-based buffer overflow exists in the TEA decoding algorithm implementation in RhinoSoft Serv-U FTP server versions 7.0.0.1, 9.0.0.5, and other versions prior to 9.1.0.0. The vulnerability is triggered when the server processes a long hexadecimal string, leading to a buffer overflow condition that can be exploited by remote attackers to execute arbitrary code.
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 (modules/exploits/windows/http/servu_session_cookie.rb) that exploits a buffer overflow vulnerability in Rhinosoft Serv-U 9.0.0.5's HTTP service (CVE-2009-4006). The exploit works by sending a specially crafted HTTP POST request with an overly long session cookie, triggering a stack-based buffer overflow and allowing arbitrary code execution. The module supports exploitation on Windows 2003 SP2 (with NX) and Windows 2000 SP4/XP SP3 (SEH) targets, using ROP chains and SEH overwrites as appropriate. The payload is user-selectable via Metasploit and is injected into the overflowed buffer. The exploit targets TCP port 80 and leverages specific DLLs (libeay32.dll, mfc90u.dll, ntdll.dll) for ROP gadgets. The module includes a check method to verify if the target is running the vulnerable Serv-U version. Overall, this is a weaponized, operational exploit module for Metasploit, providing remote code execution against vulnerable Serv-U installations.
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.