

The username provided to cPHulkd is set before this munging occurs. Hardening the check of the account now prevents the bypassing of account suspension. If the IP address was not blocked, then a success message was sent unconditionally. When authenticating via FTP, cPHulkd does not consider usernames with different junk characters as the same user for each login attempt.īecause of this, the login limit number is never reached and a block is never put into place.

The user name provided to cPHulkd is set before this munging occurs. Users will now need to enter their own two factor authentication token when logging in by possessing an account. Now static document requests are checked to be valid before the document request is passed through.īecause of this, it is possible to bypass ACLs required to run the application.
#Cpanel magic revision code#
The retrieved nameserver records were used in an insecure manner, which allowed arbitrary code execution as root during the domain alias creation process. When combined with a specifically crafted MakeText interpolated string, arbitrary code can be run as the root user.
#Cpanel magic revision password#
This behavior can be prevented by not using the password flag and entering the password during the execution of the script.Īn attacker was able to take advantage of this to inject arbitrary code into the rendered pages.

I tested this on a live server here an was unable to reproduce. You may wish to submit a ticket (see the link in my signature) so we can investigate why these requests are succeeding. None of the cPanel Magic Revision items are available over port 80 unless youve configured apache to serve pages out of usrlocalcpanel or any of its subdirectories.
#Cpanel magic revision update#

There was been no compromise on our account (e.g. Reset Password Deutsch English espaol de Espaa ien Select a locale: English. Well what they actually mean is that they nuke the whole accountįine - I get security, we live it here, so in goes the ticket to explain what this account is used for (and like all our accounts, there is no mass emailing, nor has there been) as per their exact requirements, answering all their questions. Our account is disabled for a domain in question. We wake a few days ago that something on our account has been compromised and we need contact support. So that's no mass emails, no newsletters, just things like booking confirmations and so on. We have been a loyal mailgun user for forever - and we are not just a little freebie account - we use them and pay them every month, sending around 50k transactional emails.
