# CVE-2011-1575: Other in n/a

> Man-in-the-middle attackers can inject commands into encrypted FTP sessions due to improper I/O buffering in Pure-FTPd's STARTTLS implementation.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 May 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-1575, GHSA-mqpg-5c3p-cx82

## What is CVE-2011-1575?

CVE-2011-1575 is a medium-severity vulnerability in n/a, published on 23 May 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The STARTTLS implementation in ftp_parser.c in Pure-FTPd before 1.0.30 does not properly restrict I/O buffering, which allows man-in-the-middle attackers to insert commands into encrypted FTP sessions by sending a cleartext command that is processed after TLS is in place, related to a "plaintext command injection" attack, a similar issue to CVE-2011-0411.

Weakness: CWE-399

## Which versions are affected by CVE-2011-1575?

It affects 1 product.


Products: Pureftpd Pure-Ftpd.

## How do I fix CVE-2011-1575?

Upgrade to a fixed version.

## Is CVE-2011-1575 being exploited?

There is no known exploitation of CVE-2011-1575 in the wild and no public exploit code.

Public exploit code:

- Very simple script to test for cve 2011-1575 (github_poc): https://github.com/masamoon/cve-2011-1575-poc

## Other vulnerabilities in n/a

- [CVE-2024-48208](https://insights.sbomify.com/CVE-2024-48208/): Memory corruption in n/a (high 8.6)
- [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-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-2011-1575 and fix it if it is affected.

What it is: CVE-2011-1575 is a medium-severity vulnerability in n/a, published on 23 May 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-1575 in the wild and no public exploit code.

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-2011-1575/ (Markdown: https://insights.sbomify.com/CVE-2011-1575/index.md)
```

## Sources

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

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