• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Vulnerability in ProFTP 1.3.3d (PCI Compliance)

JohnToTheK

New Pleskian
We are currently using Plesk Panel 10.0.0 on CentOS 4.9. I realize our server is well out of date, but due to extraneous circumstances, we haven't been able to update it.

While that is the case, we are still held to PCI compliance standards. One of their scans flagged our server with this:

possible vulnerability in ProFTP 1.3.3d

Risk: High (3)
Port: 20/tcp
Protocol: tcp
Threat ID: ftp_proftp

Details: Response Pool Use-After-Free Vulnerability

11/17/11
CVE 2011-4130
ProFTPD before 1.3.3g is prone to a vulnerability,
which can be exploited by malicious users to compromise a vulnerable system.
The vulnerability is caused due to a use-after-free error when handling response pool allocation lists and can be exploited to corrupt memory.
Successful exploitation may allow execution of arbitrary code.

Information From Target:
Service: ftp
Received: 220 ProFTPD 1.3.3d Server (ProFTPD)

My question is this: is it possible to upgrade ProFTPD to at least 1.3.3g on our server? We can't use the yum command anymore, since they've turned off the repositories for our outdated server. What are our options here? Thanks so much for any advice!
 
Blake, thanks so much for the reply.

Since we are currently running CentOS 4.9, we were told that we can't update past Plesk 10.0.0, where we are now. So I have been operating under the assumption that unless we change our server, we can't update Plesk anymore.

Is that true?

If that is true, is there any other option for upgrading ProFTP, outside of upgrading Plesk?
 
CentOS 4 is actually supported up to Plesk 10.2. You could update to this version and apply all MicroUpdates to get the ProFTPd fixed version. http://download1.parallels.com/Ples...nel-10-linux-updates-release-notes.html#10212

That said, given that CentOS 4 has been EOL'ed by its vendor, I think it would be in your best interests (in terms of both PCI and security overall) to get a new server with CentOS 5 or CentOS 6 with Plesk 11.x and migrate your Plesk instance to this new server at your earliest convenience.
 
Back
Top