• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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