Welcome Guest. | Log In | Register | Membership Benefits

New HTTP POST DDoS Attack Tools Released

Very slooowwww HTTP POST connections wage denial-of-service attack on Web-based servers

Nov 29, 2010 | 05:30 PM | 

By Kelly Jackson Higgins
Dark Reading
Two free tools have been unleashed that exploit the recently demonstrated slow HTTP POST attack that takes advantage of a generic flaw in HTTP -- the so-called "R U Dead Yet?" tool and the OWASP HTTP POST Tool.

Slide Show: DDoS With The Slow HTTP POST Attack
(click image for larger view)
Slide Show: DDoS With The Slow HTTP POST Attack

Researchers at last month's OWASP 2010 Application Security Conference in Washington, D.C., demonstrated how the HTTP protocol leaves the door open for attackers to wage a new form of distributed denial-of-service (DDoS) attack that floods Web servers with very slow HTTP "POST" traffic.

Researcher Wong Onn Chee, who first discovered the attack in 2009 with a team of researchers in Singapore, and Tom Brennan, a security researcher with Proactive Risk, also demonstrated how an online game could be used as a means of recruiting bots for an "agentless" botnet that executes this HTTP POST DDoS attack. Chee says HTTP is broken and that all Web-based servers or systems with a Web interface are vulnerable to this attack. "If it has a Web interface, we can knock it down [with this attack]," Chee said earlier this month.

Independent researcher Raviv Raz unleashed "R U Dead Yet?" early last week, and then Chee and Brennan pushed out their tool on Thanksgiving Day.

Ryan Barnett, senior security researcher with Trustwave's SpiderLabs, has been testing the tools and devised some mitigation strategies using the open-source ModSecurity Web application firewall and Apache, namely specifying different thresholds for receiving data. Barnett uses the timely analogy of airport security screening to explain what happens in a HTTP POST attack: Unlike a traditional denial-of-service attack where there are just too many business-type frequent flyers in line to get the traffic through quickly, he says, this new "connection consumption" type of attack is like a relatively short line of travelers going through security -- most of whom are families with kids, strollers, and other items that take longer to screen.

"And just when you think the group is going to make it through, the metal detector sounds and the whole group has to go back through the process again. This is essentially what is happening with these slow HTTP requests," Barnett says. "They are sending data very slowly, and just when the Web server's timeout thresholds are about to be exceeded, they send a little more data."

An HTTP POST attack sends POST headers that let the server know how much data is arriving, but when it does the message body is sent a very slow speed to jam the connection and sap server resources. According to Chee, this attack can take down a website within minutes using just tens of thousands of slow HTTP POST connections.

Click here to view Onn Chee and Brennan's slides from their recent OWASP presentation.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Vulnerability Management Reports

report Choosing the Right Vulnerability Scanner for Your Organization
Vulnerability scanners can be used to help detect and fix systemic problems in an organization's security program and monitor the effectiveness of security controls. However, a vulnerability scanner can improve the organization?s security posture only when it is used as part of a vulnerability management program, in which products, processes and people are working together to find, identify, prioritize and mitigate threats. Here are some tips on choosing and implementing vulnerability scanners in your enterprise.

report Using Google to Find Vulnerabilities In Your IT Environment
Attackers are increasingly using a simple method for finding flaws in websites and applications: they Google them. Using Google code search, hackers can identify crucial vulnerabilities in application code strings, providing the entry point they need to break through application security. Sound scary? It is, but there is good news: You can use these same methods to find flaws before the bad guys do. In this special report, we outline methods for using search engines such as Google and Bing to identify vulnerabilities in your applications, systems and services--and to fix them before they can be exploited.

report Security Pro's Guide to Patch Management
It's no longer sufficient to patch just Windows, Office and IE. With the massive array of applications now residing on enterprise PCs, and the proliferation of mobile and cloud-based applications, your business is far too vulnerable to exploitation unless you have a solid strategy for patch prioritization, deployment and quality assurance. Follow these steps to put your plan in place.

Other reports from the Vulnerability Management Tech Center:




Featured Webcasts
Featured Whitepapers
Featured Reports