Hi!
I'm a student doing a research with ModSecurity. I'm coming up with some
rules to prevent * HTTP POST DoS attack on the Apache server by using JavaScript
cookies. ModSecurity injects the JavaScript code on any webpage then ModSecurity
is then configured to drop requests without these cookies. My main assumption is
that most bots especially those that use the slow HTTP DoS POST attack don't use
browsers and thus don't use JavaScript.
Can anyone here give me some insights as to how effective/not effective
that prevention is? Can someone also use JavaScript to create a Slow HTTP POST
attack tool that triggers or steals that cookie and proceed with the
attack?
There are already other mitigating techniques in place. But I'm trying to
put in another layer of prevention using the open source Apache module called
ModSecurity and use its content injection capability to detect if client
requests are coming from legitimate clients like browsers and not tools often
used for DoS attacks. I assumed that most legitimate web clients would have the
complete browser technology stack would have JavaScript. I tested this against
slowhttptest from Qualys found here -
and the OWASP Slow POST Tool here -
Articles on slow post DoS attacks can be found
As far as my mitigation is concerned, it’s huge weakness is when a tool can
read JS cookies, grab them, and use them for DoS. As far as I know, other tools
can’t grab JS cookies since they run at the client-side. Unless a tool can parse
JS first, then look for document.cookie.
I need some inputs on the possibility of a proof-of-concept tool that can do a Slow HTTP request DoS using JS, or can grab JS cookies, then use them to commit Slow HTTP DoS attacks.
But I'm not sure if JS can slow down the requests.
I also haven’t found any slow http DoS tools run by a browser.
Your inputs will be appreciated.
Thanks!