The Register® — Biting the hand that feeds IT

Feeds

Tiny-traffic DoS attack spotlights Apache flaw

Denial of Service without the flood

Regcast training : Hyper-V 3.0, VM high availability and disaster recovery

Security guru Robert "RSnake" Hansen has released a novel DoS attack tool that points to a significant flaw in Apache and other webservers.

Hansen calls his creation "Slowloris - the low bandwidth yet greedy and poisonous HTTP client." Unlike an old school Denial of Service attack, which ties up a website by bombarding the thing with epic amounts of traffic, Slowloris achieves the same result with a handful of packets.

"A typical request-flooder [DoS attack] might need a 1000 machines to take down a single web server, because you need that much bandwidth to pull enough traffic to saturate the actual physical lines so no one else can come through," Rsnake tells The Reg. "But Slowloris uses almost no traffic at all. You need few 1000 packets to get started and then a few hundred on a regular integrated basis to continue - 200 to 300 packets per minute.

"You can easily do it with a single machine."

Rather than bombarding a site with traffic, Slowloris manages to hold a webserver's available connections open by sending partial http requests. "You make a request but you never actually complete the request," says Hansen, chief executive officer of security consultancy SecTheory and the man behind the online security lab ha.ckers.org. And if you send a few hundred partial requests, "Apache will wait a really long time to wait for every single on of these open connections to tell it what they want and they never do."

A webserver like Apache limits the number of threads it will open at any one time. "If they didn't do that, you could use memory exhaustion or some other form of attack," Hansen explains.

Hansen has confirmed the flaw on Apache 1.x, Apache 2.x, dhttpd, GoAhead WebServer, and Squid, but his attack doesn't affect IIS6.0, IIS7.0, or lighttpd. Webservers like IIS uses a "worker pool," allowing as many open connections as its resources will allow.

Apache did not respond to our request for comment on the bug. But Hansen has contacted the organization and says they were previously aware it. At the time of writing, they had not patched it. After posting his tool to the web, it was pointed out that another researcher described a similar attack in early 2007 - without releasing a tool that executed the attack.

According Hansen, the attack won't affect large websites equipped with load balancers using the worker pool model. "We're really only talking about a fraction of the Apache sites out there," he says. "But it's still a lot of sites. It's just not the big retail and news sites." ®

Update

Apache has responded with a comment to this story, but it does not want it to be viewed as an official response: "This is not new, and a trawl through Apache mailinglists will find a few mentions of it over the years. For example, the Event MPM effectively nullifies this attack, and was first included in a production release of Apache in 2005."

We have asked Apache to keep us updated on the matter and will update this story when we have more information.

Agentless Backup is Not a Myth

IIS

"Webservers like IIS uses a "worker pool," allowing as many open connections as its resources will allow."

But it can't have more 'resources' (aka threads) that a machine of the same spec. So we're talking again 1 to 1, or at max 2 to 1 to defeat them as well.

Apache simply allows you to configure the number of threads, so if the value is not low enough, there are no problems either. Experienced/savvy admins use stress testing tools before deployment.

Others get what they deserve.

1
0

The Event MPM is not a solution.

I know it has already been mentioned that the Event MPM is not a solution because a) it's experimental and b) it doesn't support SSL, but you are forgetting the most important point:

The Event MPM is just as vulnerable as the Pre-Fork and Worker MPMs.

0
0

Fix the bug!

I can see why they don't want Event MPM as an official comment.

http://httpd.apache.org/docs/2.2/mod/event.html

Because of:

"Warning

This MPM is experimental, so it may or may not work as expected."

and

"Issues

At present, this MPM is incompatible with mod_ssl, and other input filters."

So, it may nullify the problem, but it doesn't fix it and it is a sloppy piece of crap. They should just do a bug fix on apache instead!!!

0
0

More from The Register

 breaking news
Number of cops abusing Police National Computer access on the rise
Only a telegram from the Queen can get you off it
 breaking news
NSA PRISM snoop-gate: Won't someone think of the children, wails Apple
10,000 things probed, mostly about missing kids, Alzheimer patients, we're told
Flash flaw potentially makes every webcam or laptop a PEEPHOLE
But it's a Google problem - Chrome only, insists Adobe
 breaking news
NSA PRISM-gate: Relax, GCHQ spooks 'keep us safe', says Cameron
Whatever they are up to, it's all above board, we're told
PRISM snitch claims NSA hacked Chinese targets since 2009
Snowden suddenly looks safer in Hong Kong after revelations
 breaking news
US chief spook: Look, we only want to spy on 6.66 BEELLLION of you
Americans assured they are not in the NSA's sights
Speech-to-text drives motorists to distraction
Will talking to you mean I crash into that car up ahead, Siri?
 breaking news
Yahoo! joins! rivals! in! PRISM! data! request! admission!
Keep calm and carry on using American tech firms, folks
DHS warns of vulns in hospital medical equipment
Has your doctor's anasthesia machine been hacked?
 breaking news
'BadNews is malware' says outfit that found it
Google says code harmless but Lookout says code base is evolving