# CVE-2024-48208: Memory corruption in n/a

> An out-of-bounds read in pure-ftpd's ls.c file can lead to buffer overflow, potentially causing denial of service or code execution.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Oct 2024
- **Updated:** 28 Oct 2024
- **Also known as:** DEBIAN-CVE-2024-48208, GHSA-rrmj-qxgv-v296, UBUNTU-CVE-2024-48208, openSUSE-SU-2025:15266-1

## What is CVE-2024-48208?

CVE-2024-48208 is a high-severity memory corruption vulnerability in n/a, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-48208?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pure-ftpd` | openSUSE:Tumbleweed | All versions | 1.0.51-5.1 |

Products: Pureftpd Pure-Ftpd.

## How do I fix CVE-2024-48208?

Upgrade to a fixed version.

## Is CVE-2024-48208 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48208 exists.

Public exploit code:

- This repo contains all the work surrounding the development of the PoC for CVE-2024-48208, and how a simple OOB(Out-of-bound) read can result in jail escapes as well as broken access control. (github_poc): https://github.com/rohilchaudhry/CVE-2024-48208
- Pure-FTPd < 1.0.52 - Buffer Overflow (nuclei)

## Other vulnerabilities in n/a

- [CVE-2021-40524](https://insights.sbomify.com/CVE-2021-40524/): Denial of service in n/a (high 7.5)
- [CVE-2020-35359](https://insights.sbomify.com/CVE-2020-35359/): Denial of service in n/a (high 7.5)
- [CVE-2011-1575](https://insights.sbomify.com/CVE-2011-1575/): Other in n/a (medium 5.8)
- [CVE-2011-3171](https://insights.sbomify.com/CVE-2011-3171/): Path traversal in n/a (low 3.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-48208 and fix it if it is affected.

What it is: CVE-2024-48208 is a high-severity memory corruption vulnerability in n/a, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48208 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-48208/ (Markdown: https://insights.sbomify.com/CVE-2024-48208/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-48208
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-48208
- OSV: https://osv.dev/vulnerability/CVE-2024-48208

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-48208/
Summaries are generated and may contain mistakes; the official description above is the record.