wp-login.php Brute Force Defense
Currently observing a lot of brute force attacks trying to get access to my WordPress installation. Fortunately, I’ve been aware of such cranks when I installed WordPress, and now I want to share my technique to prevent such attacks.
What's the problem?
There are some guys who try to get access to your website’s content to distribute even more spam and malware. Since they don’t have your credentials they need to guess them. Usually they randomly choose common login names (like admin
or martin
) and popular passwords (like root123
or martin
) and try to log in to your web site. However, there are lot’s of possibilities and only a few will work, so they usually need a lot of attempts. To prevent an intrusion you should choose an uncommon user name and a strong password (not only for your WordPress installation!). Nevertheless, there is still a chance to guess the credentials, so you’ll sleep much better if you make sure that there’s no chance for an attacker to break into your site.
Deny access to wp-login.php
The idea is to reject any login from anyone but you. For instance, using apache (most common webserver) you may only allow the access to wp-login.php
from defined IP adresses:
This piece of code, included in a vhost or in an .htaccess file, will only allow connections from 1.2.3.4
to your wp-login.php
. All other requests will be forwarded to /
. You need to have the module mod_access
installed. For more information take a look at the documentation of the mod_access
. Other web servers like nginx or lighttpd have similar solutions. (And I think hope even the microsoft crap is able to do such basic stuff without much configuration overhead, but I’m too busy to read microsoft documentations…)
Workaround for dynamic IPs
As long as you’re editing your articles using static IP everything is fine. But what if you’re cursed with an NAT? Indeed, it will be very annoying if you always have to adjust this config in order to log into your WordPress management interface! Fortunately, there is a small workaround if you have SSH access to that server. Simply restrict the access to the file to connections from the server’s own IP. Thus, only connections from the server itself are able to log in. In order to get access you need to setup a tunnel to your server using SSH providing a socks proxy:
This command will create a tunnel from your local system to your.web.server
. Connections to port 8765
at your systems will be forwarded to your server, hence, connections to your wp-login.php
through the tunnel will be allowed. From now on only users having access to the server (physically or via SSH) are allowed to access you wp-login.php
:-)
There’s only one restriction left: you need to SSH to your server and you have to configure your browser to use this socks proxy before you can access WordPress. I recommend to use FoxyProxy.
Testing
Ok, let’s ensure that our config works. Try to access wp-login.php
from an IP which is not allowed to access this file, e.g. using curl
:
Since I’m not allowed to access this page I got a 302 and am redirected to /
.
Ok, what happens if I connect from an allowed host?
Excellent, 200 == allowed!
If you want to verify your proxy connections using curl pass another parameter -x socks5://127.0.0.1:PORT
to the command:
Great, everything’s fine :D
More Security
Of course you can add similar rules for other web sites or scripts. For example to restrict the access to the whole admin interface of WordPress add another restriction to the vhost
/ .htaccess
:
I’m sure you’ll find even more reasonable rules.
- apache (15) ,
- curl (8) ,
- nat (3) ,
- network (81) ,
- private (31) ,
- proxy (7) ,
- security (31) ,
- ssh (12) ,
- trick (61) ,
- wordpress (15)
Leave a comment
There are multiple options to leave a comment: