• 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!
  • 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.

What is this "security concept" all about?

schlimpf

Basic Pleskian
Hello,

I am just wondering what kind of security Plesk Panel is trying to reach with things like open_basedir etc.
As an attacker, if I can execute PHP on the server, I can just execute a perl script which then can read all dirs/files that are readable by apache from the COMPLETE server. There is as far as I know no way to prevent this with only Plesk configuration.
So basically I try to break in some CMS like WordPress, upload a PHP script with it and then I got a whole lot more possibilities as "just" messing with the httpdocs folder.
This will of course work if Perl is DISABLED for the domain.

Feedback from the Plesk team is greatly appreciated.

If anyone is concerned about his/her security and dont know how to fix issues like this, you can contact me via PM.

Best
Mario
 
Last edited:
How about a chrooted environment for the apache process and/or the PHP FastCGI processes? I think this would be a huge step forward in security and willl give plesk a killer feature that is not available on competitor software like cPanel!
 
Back
Top