Skip to main content
VulnerabilityPublished Updated

CVE-2024-48208: pure-ftpd · Out-of-bounds Read

Affects pure-ftpdSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 8.6 High : upgrade to 1.0.52 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.5% chance of exploitation in 30 days – higher than 75% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.52
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Oct 2024

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade jedisct1/pure-ftpd to 1.0.52.

Affected software

ProductAffectedFixed in
GitHubjedisct1/pure-ftpdpkg:github/jedisct1/pure-ftpdOther threatsAffected
  • <1.0.52
Fixed in
  • 1.0.52

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-48208, organizations should immediately identify all systems running pure-ftpd and verify their versions. Upgrading to pure-ftpd version 1.0.52 or later, once officially released, is the most effective mitigation. If you cannot patch yet, administrators should consider restricting FTP access via network controls such as firewalls and VPNs to limit exposure. Employing intrusion detection/prevention systems (IDS/IPS) with signatures targeting anomalous FTP traffic can help detect exploitation attempts. Additionally, monitoring FTP server logs for unusual behavior or crashes can provide early warning signs. Disabling or limiting FTP services where possible, or migrating to more secure file transfer protocols like SFTP or FTPS, reduces risk. Regular backups and incident response plans should be updated to handle potential exploitation scenarios. Finally, organizations should stay alert for public exploit disclosures and vendor patches.

Description

pure-ftpd before 1.0.52 is vulnerable to Buffer Overflow. There is an out of bounds read in the domlsd() function of the ls.c file.

References

Community reviews

Loading reviews…