Loading vulnerability…
A buffer overflow vulnerability exists in RaidenFTPD version 2.4.4005, specifically in the handling of the Server name field within the Step by step setup wizard. A local attacker can exploit this flaw by providing an overly long input to the Server name field, leading to a buffer overflow condition that may allow execution of 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 provides a working exploit for CVE-2023-39063, a SEH-based buffer overflow vulnerability in RaidenFTPD v2.4.4005 on Windows. The exploit is implemented in a single Python script ('exploit-cve-2023-39063.py'), which generates a malicious payload file ('exploit-raiden.txt'). The attacker must manually paste the contents of this file into the 'Server name' field of the RaidenFTPD setup wizard to trigger the vulnerability. Upon successful exploitation, the payload executes arbitrary code (demonstrated by launching calc.exe) on the target system. The exploit is operational, with a hardcoded shellcode payload and specific SEH overwrite targeting 'msvcp70.dll'. The attack vector is local, requiring user interaction with the vulnerable application. The repository also includes a README with usage instructions and a demonstration link, as well as standard license and .gitignore files.
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.