Note: This is an archival copy of Security Sun Alert 200229 as previously published on http://sunsolve.sun.com.|
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1000180.1.
Sun Java System Application Server Platform Edition 8.1 2005Q1
Sun Java System Application Server Platform Edition 8.1 2005Q1 Update Release 1
Sun Java System Application Server Enterprise Edition 8.1 2005Q1
Date of Resolved Release
When a deployed web application created for the Sun Java System Application Server contains a "jar" file, contents of the jar file may be exposed.
This issue can occur in the following releases:
To determine the version of Sun Java System Application server, the following command can be run:
$ <AS_INSTALL>/bin/asadmin version --verbose Unable to communicate with admin server, getting version locally. Version = Sun Java System Application Server Enterprise Edition 8.1 (build b43-fcs) Command version executed successfully.
(Where <AS_INSTALL> is the installation directory of the Application Server)
There are no reliable symptoms that would indicate the described issue has occurred.
To work around the described issue, use one of the two following methods:
A. Turn off the directory listing feature for web apps, which is on by default:
1. Edit $<AS_DOMAIN>/domain1/config/default-web.xml
2. Set the listing value to false:
3. Restart the domain
B. Delete the files that got unjarred from the jar files under $<AS_DOMAIN>/domain1/applications/j2ee-modules/<application-name>/ after deployment of the web application.
Example: If the file "com/sun/appserv/web/taglibs/cache/CacheTag.class" was packaged as appserv-tags.jar (This appserv-tags.jar file was packaged in the war file webapps-caching.war) then after deployment of the war file webapps-caching.war, delete the directory "com" under $<AS_DOMAIN>/domain1/applications/j2ee-modules/webapps-caching.
This issue is addressed in the following releases:
NOTE: The resolution outlined above will only affect applications deployed after the installation of the above patches or upgrades. To correct web applications that were deployed prior to installing the resolution, workaround "B" (in Relief/Workaround) needs to be applied to those applications.
This solution has no attachment