• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Security Auditing on Pleak 8.4

F

fatangel

Guest
Hello,

We have a Unix server with Plesk 8.4 installed. We're currently working with SecurityMetrics to tighten the security of a website. Right now, they're complaining about the services on port 8443. Example:

Synopsis : The remote web server uses a version of PHP that is affected by multiple flaws.
Description : According to its banner, the version of PHP installed on the remote host is older
than 5.2.6.

As we understand it, the various services and modules for the Plesk Control Panel (on port 8443) work separately from the services and modules for customer websites (port 80); and thus, the security vulnerabilities of the control panel do NOT affect the security of the customer's website.

However, SecurityMetrics is refusing to listen to the explanation above.

1) Is our understanding of how the server works correct?
2) Can the above be explained in a different manner that will help them understand?
3) Beyond upgrading to Plesk 8.6 are there any other ways to work around the complaints?

thanks,

Ken
 
Back
Top