Category
Security
Release Phase
Resolved
ProductSun Java System Access Manager 7.1
Bug Id
6571897
Date of Workaround Release27-SEP-2007
Date of Resolved Release10-Sep-2009
Installation of Sun Java System Access Manager 7.1 on Sun Java System Application Server 9.1 or 8.x May Compromise Application Server Security
1. Impact
There are two vulnerabilities associated with this issue:
1. When Sun Java System Access Manager 7.1 is installed in a Sun Java System Application Server 9.1 container and the container is restarted, no authentication screen is displayed. Any application using container based authentication would no longer work correctly as any users would be granted access without authentication. This can lead to unprivileged non-administrative users performing administrative tasks. As an example, the Admin Console application (which is a pre-deployed system application on the Application Server used to Administer the Application Server) no longer prompts users for authentication when accessing this application. Thus anyone, whether they have administrative privileges or no privileges, could administer the Application Server.
2. When Sun Java System Access Manager 7.1 is installed in a Sun Java System Application Server 8.x container, the installation may be vulnerable to malicious code. If an application is deployed in such an environment, then a local or remote unprivileged user may be able to execute arbitrary code with the privileges of the deployed application.
2. Contributing Factors
These issues can occur in the following releases:
SPARC Platform
- Sun Java System Access Manager 7.1 (for Solaris 8, 9 and 10) without patch 126356-01
x86 Platform
- Sun Java System Access Manager 7.1 (for Solaris 8, 9 and 10) without patch 126357-01
Linux
- Sun Java System Access Manager 7.1 without patch 126358-01
Windows
- Sun Java System Access Manager 7.1 without patch 126359-01
Note: No other versions of Sun Java System Access Manager or Sun Java System Application Server, or Access Manager 7.1 on any other Web container are affected by this issue.
These vulnerabilities may be present under any one of the following conditions:
a) If Sun Java System Access Manager 7.1 is installed in a Sun Java System Application Server 9.1 container
b) If Sun Java System Access Manager 7.1 is installed in a Sun Java System Application Server 8.x container
c) If Sun Java System Access Manager 7.1 is installed in a Sun Java System Application Server 8.x container, and then the system is upgraded to Sun Java System Application Server 9.1
d) If you performed the Sun Java System Application Server 8.x-> 9.1 upgrade between the installation of Sun Java System Access Manager 7.1 and application of Sun Java System Access Manager patch 7.1P1 (where this issue is fixed), then you are impacted.
To determine the version of Sun Java System Access Manager on a Solaris system, the following command can be run:
% pkginfo -l SUNWamsvc
PKGINST: SUNWamsvc
NAME: Sun Java System Access Manager Services
CATEGORY: application
ARCH: all
VERSION: 7.1,REV=06.12.19.15.12
To determine the version of Sun Java System Access Manager on other systems, the following command can be run:
# <access-manager-install-dir>/bin/amadmin --version
Sun Java System Access Manager 7.1
(Where <access-manager-install-dir> is the installation directory of Sun Java System Access Manager).
3. Symptoms
1. If Sun Java System Access Manager 7.1 is installed in a Sun Java System Application Server 9.1 container, the container is restarted, and no authentication screen is displayed, this vulnerability is present.
2. If Sun Java System Access Manager 7.1 is installed in a Sun Java System Application Server 8.x container, and the following 2 lines are present in the "<install-dir>/SUNWappserver/appserver/domains/domain1/config/server.policy" file:
permission java.security.AllPermission "MonitoringAuth.*";
permission java.security.AllPermission "MonitoringPolicy.*";
then this vulnerability is present.
4. Workaround
To work around the described issues, apply the following to the server.policy file located in the "<install-dir>/SUNWappserver/appserver/domains/domain1/config/server.policy" directory:
1. Remove the following lines:
permission java.security.AllPermission "MonitoringAuth.*";
permission java.security.AllPermission "MonitoringPolicy.*";
2. Add the following lines:
permission javax.management.MBeanServerPermission "*";
permission javax.management.MBeanPermission "*", "*";
permission javax.management.MBeanTrustPermission "*";
3. Add the following lines:
permission java.io.FilePermission
"$MFWK_BASEDIR_CONF/var/opt/$MFWK_PROD_DIR/logs/*", "delete,write";
(where $MFWK_BASEDIR_CONF is "/" when the default package installation directory is "/opt" (solaris), or "/opt/sun" (Linux, HP-UX).
for Windows:
permission java.io.FilePermission
"$JES5_install_dir<>\share\mfwk\logs\*", "delete,write";
(where $JES5_install_dir is the JES 5 installation directory on Windows platform)
4. Stop and restart the Application Server container
5. Resolution
This issue is addressed in the following releases:
SPARC Platform
- Sun Java System Access Manager 7.1 (for Solaris 8, 9 and 10) with patch 126356-01 or later
x86 Platform
- Sun Java System Access Manager 7.1 (for Solaris 8, 9 and 10) with patch 126357-01 or later
Linux
- Sun Java System Access Manager 7.1 with patch 126358-01 or later
Windows
- Sun Java System Access Manager 7.1 with patch 126359-01 or later
For more information on
Security Sun Alerts, see 1009886.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.
Modification History
14-Jan-2008: Updated Contributing Factors and Resolution sections
17-Jan-2008: Updated Contributing Factors and Resolution sections
29-Jan-2008: Republished
10-Sep-2009: No further updates; republished as Resolved
References
126356-01
126357-01
126358-01
126359-01
AttachmentsThis solution has no attachment