Note: This is an archival copy of Security Sun Alert 200627 as previously published on http://sunsolve.sun.com.|
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1000489.1.
Solaris 10 Operating System
6452767, 6423037, 6423033
Date of Resolved Release
Three security vulnerabilities have been found in the Apache HTTP server which affect the Apache 2.0 web server bundled with Solaris 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 2.0 process or cause a Denial of Service (DoS) to the Apache HTTP process. The Apache 2.0 HTTP process normally runs as the unprivileged user "webservd" (uid 80).
The second issue, a vulnerability in the mod_ssl Apache HTTP server module (CVE-2005-3357), may allow a local or remote unprivileged user to cause a Denial of Service (DoS) to the Apache HTTP process.
The third 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 1.3 ships with Solaris 8, 9, and 10, and is impacted by two of the issues referenced in this Sun Alert - CVE-2005-3352 and CVE-2006-3747. For details on the impact to Apache 1.3 see Sun Alert 102663.
Note 2: The Apache 2.0 web server is not bundled with releases prior to Solaris 10. However, 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: A system is only vulnerable to the described issues if the Apache 2.0 web server has been configured and is running on the system. The following SMF command can be used to see if the Solaris 10 bundled Apache 2 web server service is enabled:
$ svcs svc:/network/http:apache2 STATE STIME FMRI
disabled Feb_02 svc:/network/http:apache2
Note 4: The mod_rewrite vulnerability (CVE-2006-3747) is present in Apache 2 versions 2.0.46 to 2.0.58 and Solaris 10 bundled Apache 2 versions 2.0.46 to 2.0.58 built Aug 9 2006. The mod_ssl vulnerability (CVE-2005-3357) is present in Apache 2 versions 2.0 to 2.0.55. The mod_imap vulnerability (CVE-2005-3352) is present in Apache 2 versions 2.0 to 2.0.56.
To determine the version and build date of the Solaris bundled Apache 2 web server installed on a host, the following command can be run:
$ /usr/apache2/bin/httpd -v Server version: Apache/2.0.52 Server built: Jan 22 2006 02:10:22
Note 5: 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/apache2/httpd.conf RewriteEngine on
This option defaults to "off", therefore, if it is not present in the configuration files, the system is not affected.
Note 6: The mod_ssl vulnerability (CVE-2005-3357) only affects systems which make use of the Apache SSL module (mod_ssl). If the Apache Web Server is configured to use the 'mod_ssl' module, text similar to the following will be printed to the error log when Apache is started:
$ grep mod_ssl /var/apache2/logs/error_log [Tue Sep 26 17:23:13 2006] [notice] Apache/2.0.52 (Unix) DAV/2 mod_ssl/2.0.52 OpenSSL/0.9.7d mod_perl/2.0.0 Perl/v5.8.4 configured-- resuming normal operations
If no "mod_ssl" version information is displayed in the log when the application is started, the Apache 2 Web Server is not configured to use SSL.
Note 7: 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 been exploited on a system.
To work around the mod_imap issue (CVE-2005-3352), disable the "imap-file map" entry in the Apache 2 httpd.conf file. The "imap-file map" entry should look like:
#AddHandler imap-file map
Refer to http://httpd.apache.org/docs/2.0/mod/mod_imap.html for details.
To work around the mod_rewrite issue (CVE-2006-3747), disable the "RewriteEngine" option in the Apache 2 httpd.conf file. The RewriteEngine line should look like the following:
Refer to http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html for details.
There is no workaround for the mod_ssl issue (CVE-2005-3357).
These issues are addressed in the following releases:
This solution has no attachment