CVE-2024-48208 json
pure-ftpd before 1.0.52 is vulnerable to Buffer Overflow.
published 2024-10-24 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-42955
- cvss
- 8.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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.
Patch / fix
- pureftpd pure-ftpd 1.0.52
- pure-ftpd openSUSE Tumbleweed 1.0.51-5.1
opensuse advisories openSUSE-SU-2025:15266-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-48208 updated
pure-ftpd: out of bounds read in the domlsd() function of ls.c
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
1.56% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template Pure-FTPd < 1.0.52 - Buffer Overflow nuclei detection template
- github.com https://github.com/jedisct1/pure-ftpd/pull/176 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H |
| CNA | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H |
Affected products
- pureftpd pure-ftpd
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/jedisct1/pure-ftpd/pull/176
exploit, issue-tracking
Sources
- CVE List CVE-2024-48208
- NVD CVE-2024-48208
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.