Loading vulnerability…
A use-after-free vulnerability exists in ProFTPD 1.3.7 due to improper handling of memory pool deallocation when the data transfer channel is interrupted. Specifically, the alloc_pool function in pool.c can be triggered to operate on already freed memory, leading to memory corruption.
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 three main C files related to the exploitation of CVE-2020-9273, a heap use-after-free vulnerability in ProFTPd. The files are: - 'exploit_proftpd.c': The most complete and reliable exploit, designed for localhost testing. It achieves remote code execution by exploiting the use-after-free bug, using a custom ROP chain and reverse shell payload. The exploit requires post-authentication access and the ability to upload files. It is highly dependent on the target's memory layout and requires manual adjustment of offsets for different environments. - 'exploit_demo.c': An earlier, less complete demo exploit with hardcoded addresses, intended as a proof-of-concept. It also targets localhost and demonstrates the exploitation path but is not fully automated or reliable. - 'poc-not-really-v4.c': A detailed PoC and writeup that explains the exploitation path and memory manipulation required to trigger the vulnerability. It is intended for educational purposes and to aid in understanding the bug. The repository is focused on demonstrating and explaining the exploitation process for CVE-2020-9273 in ProFTPd, with a strong emphasis on the technical details and manual steps required to adapt the exploit to different targets. The main attack vector is network-based (FTP), but requires valid credentials and file upload capability (post-auth). The payload is a reverse shell with a password, and the exploit is operational but not fully weaponized for remote, unauthenticated exploitation. Several file and network endpoints are hardcoded for localhost testing, but can be adapted for other targets.
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.
1 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.