# CVE-2015-3306: ProFTPD Improper Access Control

> Remote attackers can read and write arbitrary files on ProFTPD servers using mod_copy commands, requiring the module to be enabled.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 8 Oct 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 May 2015
- **Updated:** 9 Oct 2026
- **Also known as:** DEBIAN-CVE-2015-3306, DSA-3263-1, GHSA-4mfj-5wr8-x32q, UBUNTU-CVE-2015-3306

## What is CVE-2015-3306?

CVE-2015-3306 is a critical path traversal vulnerability in Debian Debian Linux, published on 18 May 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The mod_copy module in ProFTPD 1.3.5 allows remote attackers to read and write to arbitrary files via the site cpfr and site cpto commands.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2015-3306?

It affects 5 products.


Products: Debian Debian Linux, Fedoraproject Fedora, Opensuse Tumbleweed, Proftpd Proftpd, Suse Linux Enterprise Server.

## How do I fix CVE-2015-3306?

Apply the vendor's patch. US federal agencies must fix it by 11 Oct 2026.

## Is CVE-2015-3306 being exploited?

Yes. Attackers have exploited CVE-2015-3306 in the wild since at least 8 Oct 2026.

Public exploit code:

- ProFTPd 1.3.5 - (mod_copy) Remote Command Execution exploit and vulnerable container (github_poc): https://github.com/t0kx/exploit-CVE-2015-3306
- Exploits the arbitrary file write bug in proftpd (CVE-2015-3306) attempts code execution (github_poc): https://github.com/nootropics/propane
- Tool for exploit CVE-2015-3306 (github_poc): https://github.com/xyk0x/cpx_proftpd
- ProFTPd 1.3.5 - File Copy (github_poc): https://github.com/davidtavarez/CVE-2015-3306
- Converted with tweaks from a metasploit module as an exercise for OSCP studying and exploit development (github_poc): https://github.com/cd6629/CVE-2015-3306-Python-PoC
- https://github.com/0xm4ud/ProFTPD_CVE-2015-3306 (github_poc): https://github.com/0xm4ud/ProFTPD_CVE-2015-3306

## Other vulnerabilities in Debian Debian Linux

- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)
- [CVE-2022-30333](https://insights.sbomify.com/CVE-2022-30333/): RARLAB UnRAR Directory Traversal (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3306 and fix it if it is affected.

What it is: CVE-2015-3306 is a critical path traversal vulnerability in Debian Debian Linux, published on 18 May 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2015-3306 in the wild since at least 8 Oct 2026.

Affected product: Debian Debian Linux. 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-2015-3306/ (Markdown: https://insights.sbomify.com/CVE-2015-3306/index.md)
```

## Sources

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

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