Apache users - Upgrade to 2.0.45 NOW

Discussion in 'other security issues & news' started by spy1, Apr 3, 2003.

Thread Status:
Not open for further replies.
  1. spy1

    spy1 Registered Member

    Joined:
    Dec 29, 2002
    Posts:
    3,139
    Location:
    Clover, SC
    http://www.apache.org/dist/httpd/Announcement2.html

    Apache 2.0.45 Released
    The Apache Software Foundation and The Apache HTTP Server Project are pleased to announce the eighth public release of the Apache 2.0 HTTP Server. This Announcement notes the significant changes in 2.0.45 as compared to 2.0.44.

    OS2 users; note that Apache 2.0 versions *including* 2.0.45 still have a Denial of Service vulnerability that was identified and reported by Robert Howard that will fixed with the release of 2.0.46, but is too important to delay announcement today. The patch http://cvs.apache.org/viewcvs/apr/file_io/os2/filestat.c.diff?r1=1.34&r2=1.35 must be applied before building on OS2. This patch will already be applied to all OS2 binaries released for Apache 2.0.45. [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0134]

    This version of Apache is principally a security and bug fix release. A summary of the bug fixes is given at the end of this document. Of particular note is that 2.0.45 addresses two security vulnerabilities, both affecting all platforms.

    Prior Apache 2.0 versions through 2.0.44 had a significant Denial of Service vulnerability that was identified and reported by David Endler <DEndler@iDefense.com>, and fixed with this release. The specific details of this issue will be published by David Endler one week from this release, on April 8th [this is the correct, revised date]. No more specific information is disclosed at this time, but all Apache 2.0 users are encouraged to upgrade now. [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0132]

    This release eliminated leaks of several file descriptors to child processes, such as CGI scripts, which could consitute a security threat on servers that run untrusted CGI scripts. This issue was identified, reported and addressed by Christian Kratzer <ck@cksoft.de> and Bjoern A. Zeeb <bz@zabbadoz.net>.
     
Loading...
Thread Status:
Not open for further replies.