Two security vulnerabilities exist in the Apache HTTP server which may affect the Apache 2.0 web server (see below for details)

Two security vulnerabilities exist in the Apache HTTP server which may affect the Apache 2.0 web server bundled with Solaris 10 and the Apache 1.3 web server bundled with Solaris 8, Solaris 9 and Solaris 10.

The first issue, a Cross Site Scripting (CSS or XSS) vulnerability in the "mod_status" Apache server module (CVE-2006-5752), may allow a local or remote unprivileged user to inject arbitrary web script or HTML. This may allow an unprivileged user to bypass access control and gain access to unauthorized data.

The second issue, a vulnerability in the Apache HTTP server daemon (CVE-2007-3304), may allow a local user to send signals to an arbitrary process resulting in a Denial of Service (DoS).

Additional information regarding these issues is available at:

The Change Log for Apache 2.0, at:

• http://www.apache.org/dist/httpd/CHANGES_2.0

The Change Log for Apache 1.3, at:

• http://www.apache.org/dist/httpd/CHANGES_1.3

CVE-2006-5752 at:

• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-5752

CVE-2007-3304 at:

• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-3304

These issues can occur in the following releases:

SPARC Platform

• Solaris 8 without patch 116973-06
• Solaris 9 without patch 113146-09
• Solaris 10 without patches 120543-10 and 122911-08

x86 Platform

• Solaris 8 without patch 116974-06
• Solaris 9 without patch 114145-08
• Solaris 10 without patches 120544-10 and 122912-08

A system is only vulnerable to the described issues if the Apache 1.3 web server and/or Apache 2.0 web server has been configured and is running on the system.

To determine if the Apache 1.3 web server is currently running on the system, the following command can be used:

    $ /usr/bin/ps -ef | grep httpd
    nobody 103892 102307 0 Jan 20 ? 0:27 /usr/apache/bin/httpd

To determine if the Solaris 10 bundled Apache 2 web server service is enabled, the following SMF command can be used:

    $ svcs svc:/network/http:apache2
    STATE          STIME    FMRI
    disabled       Feb_02   svc:/network/http:apache2

The "mod_status" vulnerability (CVE-2006-5752) only affects systems which make use of the Apache Server Status module (mod_status) and the option "ExtendedStatus" is enabled.

To determine if a system is using the Apache Server Status module (mod_status), the following command can be run for all of the configuration files that define the running Apache 1.3 and Apache 2 configuration:

    $ grep SetHandler /etc/apache/httpd.conf | grep server-status
    SetHandler server-status

    $ grep SetHandler /etc/apache2/httpd.conf | grep server-status
    SetHandler server-status

To determine if the option "ExtendedStatus" is enabled, the following command can be run for all of the configuration files that define the running Apache 1.3 and Apache 2 configuration:

    $ grep ExtendedStatus /etc/apache/httpd.conf
    ExtendedStatus On

    $ grep ExtendedStatus /etc/apache2/httpd.conf
    ExtendedStatus On

There are no predictable symptoms that would indicate the described issues have been exploited on a system.

To work around the "mod_status issue" (CVE-2006-5752), disable the "ExtendedStatus" entry in the Apache "httpd.conf" file.

There is no workaround for the Apache Web Server daemon issue (CVE-2007-3304).

These issues are addressed in the following releases:

SPARC Platform

• Solaris 8 with patch 116973-06 or later
• Solaris 9 with patch 113146-09 or later
• Solaris 10 with patches 120543-10 and 122911-08 or later

x86 Platform

• Solaris 8 with patch 116974-06 or later
• Solaris 9 with patch 114145-08 or later
• Solaris 10 with patches 120544-10 and 122912-08 or later

15-Feb-2008: now Resolved
11-JAN-2007: Updated Contributint Factors and Resolution sections

This solution has no attachment