CVE-2012-6095

CVE-2012-6095 is a low-severity vulnerability in Proftpd with a CVSS 2.0 base score of 1.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.

Key facts

• Severity: Low (CVSS 2.0 base score 1.2)
• EPSS exploit prediction: 1% (48th percentile)
• Actively exploited: Not listed in CISA KEV
• Weakness: CWE-362
• Affected product: Proftpd
• Published: 2013-01-24
• Last modified: 2026-06-16

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.

Frequently asked questions

What is CVE-2012-6095?

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.

How severe is CVE-2012-6095?

CVE-2012-6095 has a CVSS 2.0 base score of 1.2, rated low severity.

Is CVE-2012-6095 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (48th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2012-6095?

CVE-2012-6095 primarily affects Proftpd. In total, 68 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2012-6095?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2012-6095 published?

CVE-2012-6095 was published on 2013-01-24 and last updated on 2026-06-16.

References

• http://bugs.proftpd.org/show_bug.cgi?id=3841
• http://proftpd.org/docs/NEWS-1.3.5rc1
• http://secunia.com/advisories/51823
• http://www.debian.org/security/2013/dsa-2606
• http://www.openwall.com/lists/oss-security/2013/01/07/3

Affected products (68)

• cpe:2.3:a:proftpd:proftpd:*:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.0:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.0:pre10:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.0:pre9:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.0:rc1:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.0:rc2:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.0:rc3:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.1:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.2:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.2:rc1:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.2:rc2:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.2:rc3:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.3:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.4:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.5:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.5:rc1:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.5:rc2:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.5:rc3:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.6:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.6:rc1:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.6:rc2:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.7:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.7:rc1:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.7:rc2:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.7:rc3:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.8:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.8:rc1:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.8:rc2:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.9:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.9:rc1:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.9:rc2:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.9:rc3:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.10:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.10:rc1:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.10:rc2:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.2.10:rc3:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.3.0:*:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.3.0:a:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.3.0:rc1:*:*:*:*:*:*
• cpe:2.3:a:proftpd:proftpd:1.3.0:rc2:*:*:*:*:*:*

More vulnerabilities in Proftpd

• CVE-2015-3306 — Critical (CVSS 10.0): The mod_copy module in ProFTPD 1.3.5 allows remote attackers to read and write to arbitrary files via the site cpfr and…
• CVE-2010-4221 — Critical (CVSS 10.0): Multiple stack-based buffer overflows in the pr_netio_telnet_gets function in netio.c in ProFTPD before 1.3.3c allow…
• CVE-2010-20103 — Critical (CVSS 9.8): A malicious backdoor was embedded in the official ProFTPD 1.3.3c source tarball distributed between November 28 and…
• CVE-2019-12815 — Critical (CVSS 9.8): An arbitrary file copy vulnerability in mod_copy in ProFTPD up to 1.3.5b allows for remote code execution and…
• CVE-2011-4130 — Critical (CVSS 9.0): Use-after-free vulnerability in the Response API in ProFTPD before 1.3.3g allows remote authenticated users to execute…
• CVE-2020-9273 — High (CVSS 8.8): In ProFTPD 1.3.7, it is possible to corrupt the memory pool by interrupting the data transfer channel. This triggers a…

All CVEs affecting Proftpd →

Other CWE-362 (Race Condition) vulnerabilities

• CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
• CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
• CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
• CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
• CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
• CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…

Browse all CWE-362 (Race Condition) vulnerabilities →