Note: This is an archival copy of Security Sun Alert 201079 as previously published on http://sunsolve.sun.com.|
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1000801.1.
Solaris 9 Operating System
Solaris 10 Operating System
Solaris 8 Operating System
6452767, 6423037, 6423033
Date of Workaround Release
Date of Resolved Release
Two security vulnerabilities have been found in the Apache HTTP server which affect the Apache 1.3 web server bundled with Solaris 8, 9, and 10.
The first issue, a vulnerability in the mod_rewrite Apache HTTP server module (CVE-2006-3747), may allow a local or remote unprivileged user to execute arbitrary code with the privileges of the Apache 1.3 process, or cause a Denial of Service (DoS) to the Apache HTTP process. The Apache process normally runs as the unprivileged user "nobody" (uid 60001).
The second issue, a Cross Site Scripting (CSS or XSS) vulnerability in the mod_imap Apache HTTP server module (CVE-2005-3352), may allow a local or remote unprivileged user to steal cookie information, hijack sessions, or cause a loss of data privacy between a client and the server.
Additional information regarding these issues is available at:
These issues can occur in the following releases:
Note 1: Apache 2.0 ships with Solaris 10 and is impacted by the issues referenced in this Sun Alert. For details on the impact to Apache 2.0 see Sun Alert 102662.
Note 2: A system is only vulnerable to these issues if the Apache 1.3 web server has been configured and is running on the system. The following command can be executed to determine if the Apache(1M) httpd daemon is currently running on the system:
$ /usr/bin/ps -ef | grep httpd nobody 103892 102307 0 Jan 20 ? 0:27 /usr/apache/bin/httpd
The Solaris bundled Apache 1.3 web server will start automatically at boot time if the file "/etc/apache/httpd.conf" exists, and "/etc/rc3.d/S50apache" has not been disabled.
Customers who have built and/or installed a vulnerable version of Apache on any version of Solaris are at risk. Refer to http://httpd.apache.org/security_report.html for information about vulnerable unbundled Apache versions.
Note 3: The mod_rewrite vulnerability (CVE-2006-3747) is present in Apache versions 1.3.28 to 1.3.36 and Solaris 10 bundled Apache 1.3 versions 1.3.28 to 1.3.35, Solaris 9 bundled Apache 1.3 versions 1.3.28 to 1.3.35.
The mod_rewrite vulnerability is addressed in the patches listed in the "Resolution" section of this Sun Alert which update Apache 1.3 to 1.3.36 built Sep 5 2006 for Solaris 10.
To determine the version and build date of the Solaris bundled Apache 1.3 web server installed on a host, the following command can be run:
$ /usr/apache/bin/httpd -v Server version: Apache/1.3.31 (Unix) Server built: Jun 30 2005 05:48:24
Note 4: The mod_rewrite vulnerability (CVE-2006-3747) only affects systems which make use of the Apache URL Rewriting Engine module (mod_rewrite). To determine if this module is enabled, a command such as the following can be run for all of the configuration files that define the running Apache configuration:
$ grep RewriteEngine /etc/apache/httpd.conf RewriteEngine on
This option defaults to "off", therefore, if it is not present in the configuration files, the host is not affected.
Note 5: The mod_imap vulnerability (CVE-2005-3352) only affects systems which make use of the Apache IMAP module (mod_imap) along with image map files. To determine if the mod_imap module is enabled for use with image map files, a command such as the following can be run for all of the configuration files that define the running Apache configuration:
$ grep 'imap-file map' /etc/apache2/httpd.conf #AddHandler imap-file map
This option is not enabled by default as the initial hash sign '#' indicates.
There are no predictable symptoms that would indicate the described issues have occurred.
To workaround the mod_rewrite issue (CVE-2006-3747), disable the "RewriteEngine" option in the Apache 1.3 httpd.conf file. The RewriteEngine line should look like:
Refer to http://httpd.apache.org/docs/1.3/mod/mod_rewrite.html for details.
To workaround the mod_imap issue (CVE-2005-3352), disable the "imap-file map" entry in the Apache 1.3 httpd.conf file. The "imap-file map" entry should look like:
#AddHandler imap-file map
Refer to http://httpd.apache.org/docs/1.3/mod/mod_imap.html for details.
These issues are addressed in the following releases:
This solution has no attachment