Cross Site Scripting (XSS) Vulnerabilities in the Apache 1.3 and 2.0 "mod_imap" and "mod_status" Modules



Category :Security
Release Phase :Resolved
Bug Id :6644748, 6644749  
Date of Workaround Release :28-Feb-2008 
Date of Resolved Release :05-May-2008 
Product :Solaris 8 Operating System
Solaris 9 Operating System
Solaris 10 Operating System  

Cross Site Scripting (XSS) Vulnerabilities in the Apache 1.3 and 2.0 "mod_imap" and "mod_status" Modules


1. Impact

Two security vulnerabilities have been found in the Apache HTTP server which 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_imap" Apache server module (CVE-2007-5000), may allow a local or remote unprivileged user to inject arbitrary web script or HTML. This may allow the unprivileged user to bypass access control and gain access to unauthorized data.

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

Additional information regarding these issues is available at:

2. Contributing Factors

These issues can occur in the following releases:

SPARC Platform
x86 Platform
Note 1: 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.

The following command can be run to determine if the Apache 1.3 web server 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 following SMF (smf(5)) 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 2: The mod_imap vulnerability (CVE-2007-5000) only affects systems which make use of the Apache Server Status module mod_imap.

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 1.3 and Apache 2 configuration:
$ egrep "imap-file|application/x-httpd-imap" /etc/apache/httpd.conf | grep map
AddType application/x-httpd-imap map
$ egrep "imap-file|application/x-httpd-imap" /etc/apache2/httpd.conf | grep map 
AddHandler imap file map
Note 3: The mod_status vulnerability (CVE-2007-6388) only affects systems which make use of the Apache Server Status module (mod_status).

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 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

3. Symptoms

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

4. Workaround

To avoid the mod_imap issue (CVE-2007-5000) from occurring, make sure that there is no activation of map files (see Note 2 in Section 2) in the Apache httpd.conf file.

To avoid the mod_status issue (CVE-2007-6388) from occurring, make sure that the "ExtendedStatus" entry in the Apache httpd.conf file is disabled.

5. Resolution

This issue is addressed in the following releases:

SPARC Platform
x86 Platform
For more information on Security Sun Alerts, see Technical Instruction ID 213557.

This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.



Modification History

25-Apr-2008: Updated Contributing Factors and Resolution sections
28-Apr-2008: Updated Resolution section to add link for Security Technical Instruction doc
05-May-2008: Updated Contributing Factors and Resolution sections: RESOLVED




Attachments
This solution has no attachment

 
 
Login Required

You must login and have a valid contract to access Sun's Premium content which includes:

  • Sun Alerts
  • Bugs
  • Patches
  • Solutions
  • White Papers
  • Documentation
  • Support Knowledge

Login Required

You must login and have a valid contract to access Sun's contracted features

Access Legend:

(Login to access)   Sun Contracted Content
(Login to access)   Sun Contracted Feature

Please make use of SunSolve Feedback application by selecting the floating [+] to provide feedback about this specific document.

Search

Article Details
Article ID : 233623
Article Type : Sun Alert
Last reviewed : 2010-01-20
Audience : PUBLIC
Keywords :
Provide feedback  (help)
Page Tools
»  Print This Page
»  Email This Article
»  Bookmark This Article