Loading vulnerability…
CVE-2024-48208 affects pure-ftpd before version 1.0.52. The vulnerability is an out-of-bounds read in the domlsd() function in ls.c. The provided content characterizes it as a buffer overflow, but the specific flaw described is an out-of-bounds read, indicating that the function can read memory beyond the intended buffer boundary while processing directory listing functionality.
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 full proof-of-concept (PoC) exploit for CVE-2024-48208, a vulnerability in pure-ftpd 1.0.50 that allows an out-of-bounds (OOB) read, which can be leveraged to escape chroot jails and break access control. The exploit is operational and automates the attack process using Python scripts (notably pure.py and dev_files/working_exploit.py). The attack requires the attacker to have valid credentials for a restricted user and SSH access to the server to create a malicious symlink pointing outside the jail. The exploit then uses the FTP MLSD command with a crafted payload to trigger the OOB read, allowing the attacker to list files in directories they should not have access to. The repository includes setup scripts (Dockerfile, chrootsetup.sh, VMsetup.txt) for building a vulnerable environment, as well as documentation (README.md, DOCKER.md) explaining the vulnerability and exploitation steps. The main attack vector is network-based, targeting the FTP service (port 21) and leveraging SSH (port 22) for setup. The exploit is not weaponized but is fully operational and demonstrates a real-world privilege escalation and jail escape scenario.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.