Couldn't you just target pretty much any dynamic page on the web with such a
script? All you'd have to do is edit a few details.
I don't understand how this qualifies as a security hole?
afaik, there is no hardcoded workaround other than disable anonymous
registration, using .htaccess/httpd.conf restrictions, or removing
wp-register.php
for the time being, if you're using mod_security, you can block it using
something like this:
SecFilterSelective THE_REQUEST wp-register.php
If you have the register user functionality disabled, like I do, you can
rename wp-register.php to something else. This workaround prevented the
DoS for me, and will hold you over until the developers have a chance to
address this.
Don
[EMAIL PROTECTED] wrote:
--
HYSA-2006-005 h4cky0u.org Advisory 014
--
Date - Wed March 08 2006
TITLE:
==
WordPress 2.0.1 Remote DoS Exploit
SEVERITY:
=
Medium
SOFTWARE:
=
Wordpress
if you're using mod_security, try a variant of this ruleset:
SecFilterSelective THE_REQUEST wp-register.php id:1004,deny,log,status:412
#SecFilterRemove 1004 - use this to remove the rule per virtual host,
uncommented.
