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

Issue How to stop cron abuse?

tkalfaoglu

Silver Pleskian
Server operating system version
Rocky Linux 8.9
Plesk version and microupdate number
Obsidian latest
Hello there. I found out some cron job belonging to a customer when I went into PLESK settings:
I can't post it as this server won't accept it, but it's a one liner that downloads a file from some hellodolly site and runs it

this was put into their crontab even though the owner of that domain does not have permission to schedule jobs according to PLESK.
I believe cron can protect itself from such jobs using /etc/cron.d/cron.allow and deny files.
What would be the required users to put into the allow file for plesk?
I assume root and psaadm?

Regards, -turgut
 
The problem can be that path traversal is done by a malicious PHP script, and the directory where the cron files are stored can be reached. New cron files can be written to it. These will then show up as new cron jobs in the scheduler. The newer the PHP version, the less danger there is. In PHP versions 5.6 or older it was very easy to break out of the base URL jail. In newer versions it became more difficult, but I would not guarantee for that it cannot be done. So if you still have old PHP running on your server, a first good step is to remove it.
 
Back
Top