Pure-Ftpd vulnerabilitiesRanked by how likely they are to be used.
Pure-Ftpd is made by Pureftpd. We track 11 published vulnerabilities in it, across 113 versions. None of them is on the list of flaws known to be exploited today. If you run Pure-Ftpd, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Pure-Ftpd vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Pure-Ftpd's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Pure-Ftpd flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 33%CVE-2011-1575Medium
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...
- 7.3%CVE-2011-0418Medium
The glob implementation in Pure-FTPd before 1.0.32, and in libc in NetBSD 5.1, does not properly expand expressions containing curly brackets, which allows remote authenticated users to cause a denial of service...
- 7.1%CVE-2020-9365High
An issue was discovered in Pure-FTPd 1.0.49.
- 6.0%CVE-2020-9274High
An issue was discovered in Pure-FTPd 1.0.49.
- 4.5%CVE-2020-35359High
Pure-FTPd 1.0.48 allows remote attackers to prevent legitimate server use by making enough connections to exceed the connection limit.
- 4.4%CVE-2019-20176High
In Pure-FTPd 1.0.49, a stack exhaustion issue was discovered in the listdir function in ls.c.
- 4.3%CVE-2021-40524High
In Pure-FTPd before 1.0.50, an incorrect max_filesize quota mechanism in the server allows attackers to upload files of unbounded size, which may lead to denial of service or a server hang.
- 1.6%CVE-2024-48208High
pure-ftpd before 1.0.52 is vulnerable to Buffer Overflow.
- 1.5%CVE-2017-12170Critical
Downstream version 1.0.46-1 of pure-ftpd as shipped in Fedora was vulnerable to packaging error due to which the original configuration was ignored after update and service started running with default configuration.
- 0.6%
Directory traversal vulnerability in pure-FTPd 1.0.22 and possibly other versions, when running on SUSE Linux Enterprise Server and possibly other operating systems, when the Netware OES remote server feature is...
Running Pure-Ftpd? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Pure-Ftpd on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 11 published vulnerabilities listed under the name Pure-Ftpd, across 113 versions.
None of Pure-Ftpd's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Pure-Ftpd. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.