# CVE-2011-4130: Use after free in n/a

> Remote authenticated users can execute arbitrary code via a use-after-free vulnerability in the ProFTPD Response API.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Dec 2011
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-4130, DSA-2346-1, DSA-2346-2, GHSA-jmgj-wg56-hjr9

## What is CVE-2011-4130?

CVE-2011-4130 is a critical use after free vulnerability in n/a, published on 6 Dec 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Use-after-free vulnerability in the Response API in ProFTPD before 1.3.3g allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

Weakness: CWE-399

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

It affects 1 product.


Products: Proftpd Proftpd.

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

Upgrade to a fixed version.

## Is CVE-2011-4130 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4221](https://insights.sbomify.com/CVE-2010-4221/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-20103](https://insights.sbomify.com/CVE-2010-20103/): ProFTPD 1.3.3c Backdoor Command Execution (critical 9.3)
- [CVE-2026-63090](https://insights.sbomify.com/CVE-2026-63090/): ProFTPD mod_sftp Heap Buffer Overflow via SFTP Packet Reassembly (high 8.7)
- [CVE-2026-35025](https://insights.sbomify.com/CVE-2026-35025/): ProFTPD ACL Bypass via /proc/self/root Path Prefix in RNFR (high 8.6)
- [CVE-2026-42167](https://insights.sbomify.com/CVE-2026-42167/): SQL injection in ProFTPD (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4130 and fix it if it is affected.

What it is: CVE-2011-4130 is a critical use after free vulnerability in n/a, published on 6 Dec 2011. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-4130 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-4130/ (Markdown: https://insights.sbomify.com/CVE-2011-4130/index.md)
```

## Sources

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

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