-
Notifications
You must be signed in to change notification settings - Fork 89
Description
Dont know where else to put this, but did want to report that today found an attacker specifically targeting hashover eg with requests ala
/HASHOVER-NEXT/backend/comments-ajax.php?instance=1&jsonp=1&jsonp_object=HashOver&time=17:5&title=User%20Experiences%20%26%20Testimonials&url=DELETED
which did manage to successfully make 34 posts - all into same url, with content typically being just "1". There were other attempts to other urls which although giving '200' status in server log did not actually create a post (I have not looked into reason why)
and also many others which gave 404 errors ala
/HASHOVER-NEXT/backend/comments-ajax.php?instance=1&jsonp=1&jsonp_object=HashOver&time=17:5&title=User%20Experiences%20%26%20Testimonials&url=DELETED'%7C%7CDBMS_PIPE.RECEIVE_MESSAGE(CHR(98)%7C%7CCHR(98)%7C%7CCHR(98)%2C15)%7C%7C'
/HASHOVER-NEXT/backend/comments-ajax.php?instance=1&jsonp=1&jsonp_object=HashOver&time=17:5&title=User%20Experiences%20%26%20Testimonials'%7C%7CDBMS_PIPE.RECEIVE_MESSAGE(CHR(98)%7C%7CCHR(98)%7C%7CCHR(98)%2C15)%7C%7C'&url=DELETED
I happened to be on-line when this occurred and was made aware of problem, at which I put ip on blacklist - at that point had been on my website for 80 minutes - during that time the attacker had 7,981 successfully reaching website with 11,138 being rejected by my security (ModSecurity,...). For hashover-specific requests, 396 gave a '200' code, 1698 a '400' code, and 3,933 were rejected by my security.