blob: ddda1cd8126550dac5f96a1766c678feaaf691ae [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200409-21">
<title>Apache 2, mod_dav: Multiple vulnerabilities</title>
Several vulnerabilities have been found in Apache 2 and mod_dav for Apache
1.3 which could allow a remote attacker to cause a Denial of Service or a
local user to get escalated privileges.
<product type="ebuild">apache</product>
<announced>September 16, 2004</announced>
<revised>December 30, 2007: 02</revised>
<package name="www-servers/apache" auto="yes" arch="*">
<unaffected range="ge">2.0.51</unaffected>
<unaffected range="lt">2.0</unaffected>
<vulnerable range="lt">2.0.51</vulnerable>
<package name="net-www/mod_dav" auto="yes" arch="*">
<unaffected range="ge">1.0.3-r2</unaffected>
<vulnerable range="le">1.0.3-r1</vulnerable>
The Apache HTTP server is one of most popular web servers on the internet.
mod_ssl provides SSL v2/v3 and TLS v1 support for it and mod_dav is the
Apache module for Distributed Authoring and Versioning (DAV).
A potential infinite loop has been found in the input filter of mod_ssl
(CAN-2004-0748) as well as a possible segmentation fault in the
char_buffer_read function if reverse proxying to a SSL server is being used
(CAN-2004-0751). Furthermore, mod_dav, as shipped in Apache httpd 2 or
mod_dav 1.0.x for Apache 1.3, contains a NULL pointer dereference which can
be triggered remotely (CAN-2004-0809). The third issue is an input
validation error found in the IPv6 URI parsing routines within the apr-util
library (CAN-2004-0786). Additionally a possible buffer overflow has been
reported when expanding environment variables during the parsing of
configuration files (CAN-2004-0747).
<impact type="normal">
A remote attacker could cause a Denial of Service either by aborting a SSL
connection in a special way, resulting in CPU consumption, by exploiting
the segmentation fault in mod_ssl or the mod_dav flaw. A remote attacker
could also crash a httpd child process by sending a specially crafted URI.
The last vulnerabilty could be used by a local user to gain the privileges
of a httpd child, if the server parses a carefully prepared .htaccess file.
There is no known workaround at this time.
All Apache 2 users should upgrade to the latest version:
# emerge sync
# emerge -pv ">=www-servers/apache-2.0.51"
# emerge ">=www-servers/apache-2.0.51"</code>
All mod_dav users should upgrade to the latest version:
# emerge sync
# emerge -pv ">=net-www/mod_dav-1.0.3-r2"
# emerge ">=net-www/mod_dav-1.0.3-r2"</code>
<uri link="">CAN-2004-0747</uri>
<uri link="">CAN-2004-0748</uri>
<uri link="">CAN-2004-0751</uri>
<uri link="">CAN-2004-0786</uri>
<uri link="">CAN-2004-0809</uri>
<metadata tag="requester" timestamp="Thu, 9 Sep 2004 04:54:03 +0000">
<metadata tag="submitter" timestamp="Fri, 10 Sep 2004 18:02:25 +0000">
<metadata tag="bugReady" timestamp="Thu, 16 Sep 2004 20:45:09 +0000">