Security Vulnerability in the Apache 1.3 "mod_jk" Module may Lead to Unauthorized Access to Data |
|
| Category : | Security |
| Release Phase : | Resolved |
| Bug Id : | 6828821
|
| Product : | Solaris 9 Operating System Solaris 10 Operating System
|
| Date of Resolved Release : | 25-Jun-2009
|
Security Vulnerability in the Apache 1.3 "mod_jk" Module ... (see below for details)
1. Impact
Security vulnerability has been found in the Tomcat Connector (mod_jk)
module for Apache HTTP server which affects the Apache 1.3 web server
bundled with Solaris 10 and Solaris 9.
This issue may allow a remote unprivileged user who provides a specially crafted
HTTP requests to bypass access control and gain access to unauthorized data.
Additional information regarding this issue is available at:
CVE-2008-5519 at: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5519
2. Contributing Factors
This issue can occur in the following releases:
SPARC Platform
- Solaris 10 with patch 122911-12 or later and without patch 122911-16
- Solaris 9 with patch 114016-02 or later and without patch 114016-04
x86 Platform
- Solaris 10 with patch 122912-12 or later and without patch 122912-16
- Solaris 9 with patch 114017-02 or later and without patch 114017-04
Note 1: A system is only vulnerable to the described issue 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 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
Note 2: The vulnerability only affects systems which make use of the
Apache 1.3 module mod_jk.
To determine if the mod_jk module is used, a command such as the
following can be run to search the Apache configuration files for
the use of the Tomcat connector. This should be repeated for all of
the configuration files that define the running Apache 1.3 configuration:
$ grep mod_jk.so /etc/apache/tomcat.conf
LoadModule jk_module libexec/mod_jk.so
Note 3: Solaris 8 does not include the "mod_jk" module and so it is not impacted by this issue.
Note 4: OpenSolaris never included version of Apache 1.3 module "mod_jk"
which is vulnerable to this issue and thus it is not impacted.
3. Symptoms
There are no predictable symptoms that would indicate that this issue has been exploited.
4. Relief/Workaround
There is no workaround for this issue.
5. Resolution
This issue is resolved in the following releases:
SPARC Platform
x86 Platform
For more information on Security Sun Alerts, see Technical Instruction
ID 213557http://sunsolve.sun.com/search/document.do?assetkey=1-61-213557-1
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-2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.
AttachmentsThis solution has no attachment