Home Business IT Open Source Debian patches Apache bug, upstream yet to react

Debian patches Apache bug, upstream yet to react

The Debian GNU/Linux project has issued a patch so its users can fix the denial of service vulnerability in the open source Apache httpd server that was announced by the Apache Software Foundation last week.

An exploit for this vulnerability is available in the wild and has been observed to have been used, according to the ASF's original announcement, which said a fix would be issued within 48 hours. That was last Thursday.

It must be mentioned here that, in its advisory, the ASF had mentioned several workarounds to mitigate against the bug being exploited. The Debian patch is based on these workarounds.

The ASF did not respond to a request for comment from iTWire.

If a web server running Apache is sent a large number of requests for overlapping byte regions of a single file download, that server would run out of memory and be rendered unable to do its job.

The Debian advisory, issued by Stefan Fritsch on behalf of the security team, said the fix issued patched both the problem with Range header and also an older bug.

Debian has a number of streams of development and a fix for the testing stream is yet to be issued. All other streams have been patched.

Once the upstream developers issue a fix, it normally takes at least 12 to 24 hours for each Linux distribution to issue its own specific fix; the same applies to other platforms.

Rick Moen, a seasoned UNIX systems administrator from California, said it was likely that the Apache developers were taking their time as the workarounds suggested by them had fixed the problem.

"It seems there is still ongoing discussion of what mix of limitations on the Range function are best used in the 2.2.x production releases, of the several that are already used in 2.3.x beta versions plus several others," Moen said.

"The developers seem to be simultaneously aware that they're overdue on the promised update, and also that it really doesn't matter much, since people have already deployed the suggested workarounds."



Moen said that the bug was not so much an Apache vulnerability, as one in the httpd protocol itself. "That is, (the) IETF (Internet Engineering Task Force) included that functionality in the HTTP 1.1 specification (RFC 2616), apparently not mindful of its abuse possibilities. There has been discussion of those possibilities for the past four years, but with no urgency until the recent emergence of an extremely efficient attack script, that can overwhelm a server by requesting many tiny overlapping byte ranges, each requested to be gzipped."

Polish security researcher Michal Zalewski warned of the possibility of this bug being exploited more than four years ago, pointing out that both Apache and Microsoft's Internet Information Services (IIS) had what he described as "a bizarro implementation of HTTP/1.1 'Range' header functionality".

"Their implementations allow the same fragment of a file to be requested an arbitrary number of times, and each redundant part to be received separately in a separate multipart/byteranges envelope," Zalewski said in a post to the Bugtraq security mailing list.

Moen added that the Apache httpd was targeted because of its popularity and its storage of pending requests in-RAM in internal "bucket brigades". "Some of the upcoming improvements will make Apache handle its 'bucket brigades' more efficiently, but the larger problem is the one inherent in HTTP itself. IETF have begun a task to refine RFC 2616's definition of Range requests to reduce their ability to be abused for DoSing."

He said it was an interesting question whether other HTTP daemons might be similarly vulnerable to DoS, simply on account of correctly implementing RFC 2616.

"This would hardly be the first time that real-world considerations lead to curtailing of Internet functionality mandated by RFCs that have become too widely abused. For example, in RFC 5321, one of the internet standards defining SMTP, sections 2.3.5, 3.1, 4.1.1.3, and 4.5.1 require that any internet domain handling SMTP mail accept all mail addressed to 'postmaster', as a point of contact for mail problems.

"Similarly, RFC  2142 section 1, paragraph 1, and section 5 require that such Internet   domains accept all mail addressed to 'abuse' as a point of contact about inappropriate public user behaviour.  _However_, because of the spam problem, most diligent postmasters aggressively block spam inbound to   'postmaster' and 'abuse'; otherwise, those mailboxes would quickly become unreadable.

"In fact, a number of large providers starting with Google's GMail no longer respect those RFCs at all: Google requires that anyone seeking  to report GMail user misbehaviour fill out a rather irksome web form, an outright violation of RFC 2142's letter and spirit."

Apache is by far the most widely used web server software and runs on all major operating systems. According to the internet services company, Netcraft, which conducts a monthly web survey, a little less than two-thirds of the websites it received a response from in August - a total of 301,771,518 - were running Apache. Responses were received from 463,000,317 sites in all.

LEARN HOW TO BE A SUCCESSFUL MVNO

Did you know: 1 in 10 mobile services in Australia use an MVNO, as more consumers are turning away from the big 3 providers?

The Australian mobile landscape is changing, and you can take advantage of it.

Any business can grow its brand (and revenue) by adding mobile services to their product range.

From telcos to supermarkets, see who’s found success and learn how they did it in the free report ‘Rise of the MVNOs’.

This free report shows you how to become a successful MVNO:

· Track recent MVNO market trends
· See who’s found success with mobile
· Find out the secret to how they did it
· Learn how to launch your own MVNO service

DOWNLOAD NOW!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.