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

Login plesk 'admin' lock attack possible ?

B

BoXie

Guest
Hi,

Is this possible ? If yes ... please fix this a.s.a.p. !!!!

Situation:
-------------
I look for a Plesk hoster find his login-screen and start a login procedure for 'admin' every 20 seconds. After X-times .. admin account will be locked for about 30 minutes.

After that I go back and lock the admin account again (by logging in 3 times with wrong credentials.).

This way, Plesk admin's cannot access their Plesk anymore (at least .. not that simple).

Can Plesk hosters be harassed like this in combination with a simple script ?

SO: is admin-locking IP-sensitive or not ?

If not --> serious problem.
 
You can lock down admin logins to use a blacklist whitelist if you go to SERVER->ACCESS. If someone were to try this, you could simply blacklist their IP, or whitelist your own range, and block everyone else. The server admin can always unlock a session by removing it from the DB as well.

Just like any DoS attack, mitigation at the network level is key.
 
Back
Top