Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2007.0737 -- [Win][Linux][HP-UX][Solaris]
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
13 February 2008
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Sun Java System Access Manager 7.1
Publisher: Sun Microsystems
Operating System: HP-UX
Linux variants
Solaris
Windows
Impact: Execute Arbitrary Code/Commands
Inappropriate Access
Access: Remote/Unauthenticated
CVE Names: CVE-2007-5152 CVE-2007-5153
Original Bulletin:
http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-26-103069-1
Revision History: February 13 2008: Corrected ESB number & corrected
Origional Bulletin
January 22 2008: Sun Updated Contributing Factors and
Resolution sections
January 16 2008: Updated the Contributing Factors to
provide more detail on vulnerable
systems. Updated the Resolution to list
the patches that are now available.
October 2 2007: Added CVE Name
October 2 2007: Added CVE Name
October 1 2007: Initial Release
- --------------------------BEGIN INCLUDED TEXT--------------------
Sun(sm) Alert Notification
* Sun Alert ID: 103069
* Synopsis: 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
* Category: Security
* Product: Sun Java System Access Manager 7.1
* BugIDs: 6571897
* Avoidance: Patch, Workaround
* State: Workaround
* Date Released: 27-Sep-2007
* Date Closed:
* Date Modified: 14-Jan-2008, 17-Jan-2008
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
HP-UX
* Sun Java System Access Manager 7.1
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.p
olicy" file:
permission java.security.AllPermission "MonitoringAuth.*";
permission java.security.AllPermission "MonitoringPolicy.*";
then this vulnerability is present.
4. Relief/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.p
olicy" 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
A final resolution is pending completion.
Change History
14-Jan-2008:
* Updated Contributing Factors and Resolution sections
17-Jan-2008:
* Updated Contributing Factors and Resolution sections
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-2006 Sun Microsystems, Inc., 4150 Network Circle, Santa
Clara, CA 95054 U.S.A. All rights reserved
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
http://www.auscert.org.au/render.html?cid=1980
If you believe that your computer system has been compromised or attacked in
any way, we encourage you to let us know by completing the secure National IT
Incident Reporting Form at:
http://www.auscert.org.au/render.html?it=3192
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQCVAwUBR7Jp9ih9+71yA2DNAQItsQP/fOo/v2MLPUBvKNm1A/qVl6gIj+zZ77E2
bLotDJ81C4FZNz8IqH5eM9MozFpSNyZsR3dJW7n7Bgmc1A14bxS9hBBFbl2o6eCV
G6u7buyx6w+WxlpWWZUApDxcTngNEZqElsivgh7lbYd8RO0dQnsJKaB4IndOh8jR
LECxPQsSwjU=
=jxcR
-----END PGP SIGNATURE-----