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

Dont allow a domain in another users account to be created as a sub in another client

Amin Taheri

Golden Pleskian
Plesk Certified Professional
So I found out that if clientA has domain.com in their account, clientB can setup host1.domain.com in their account.

Then this client can setup a website, and email, etc and possibly even phish with it.

Typically this wont be a problem unless there is a dns record explicitly set for that host, but lots of registrars include a * (star) record, meaning any non defined host records resolves to X

So a lot of people I have seen just set the * record to the web server so that they dont have to manage DNS for each sub domain they setup.

This then creates the possibility of that problem.

Repro steps (any server, any os, plesk 8.1.1)

Login as clientA account
Add domain.com to the clientA account
Log out as clientA

Login as new clientB account
Add client.domain.com to the client account

Expected result: Should fail as the root sld/tld is used on the server in another account already

Actual result: Succeeds and allows for continuation into setup of redirection or physical hosting. Once done, you can also setup email accounts

According to Plesk support this is a known "feature" - personally I see this as a potential security hole and it would be nice if this behavior was disabled by default with the option to enable it. Currently it is enabled by default with no option to disable.
 
I can think of situations where you would want to allow sub1.domain.com and sub2.domain.com being under different client accounts. Plesk automatically creates A records for subdomains, but if DNS is hosted externally it is of course very tempting to setup wildcard DNS. Tricky...
 
Yes, there are plenty of situations when it may be wanted, but its better security to disallow these types of things by default and allow them to be enabled when needed instead of by default.
 
Back
Top