# CVE-2012-6095: Race condition in n/a

> Local attackers can modify arbitrary file ownership via a race condition in ProFTPD when the UserOwner directive is enabled.

- **Severity:** Low 1.2 (`AV:L/AC:H/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jan 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-6095, DSA-2606-1, GHSA-c2hf-xq5q-pvf6

## What is CVE-2012-6095?

CVE-2012-6095 is a low-severity vulnerability in n/a, published on 24 Jan 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ProFTPD before 1.3.5rc1, when using the UserOwner directive, allows local users to modify the ownership of arbitrary files via a race condition and a symlink attack on the (1) MKD or (2) XMKD commands.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2012-6095?

It affects 1 product.


Products: Proftpd Proftpd.

## How do I fix CVE-2012-6095?

Upgrade to a fixed version.

## Is CVE-2012-6095 being exploited?

There is no known exploitation of CVE-2012-6095 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-2011-4130](https://insights.sbomify.com/CVE-2011-4130/): Use after free in n/a (critical 9.0)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6095 and fix it if it is affected.

What it is: CVE-2012-6095 is a low-severity vulnerability in n/a, published on 24 Jan 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-6095 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-2012-6095/ (Markdown: https://insights.sbomify.com/CVE-2012-6095/index.md)
```

## Sources

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

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