Fix (APAR):  PK13792

Status:  Fix

Release:  5.1.1.8,5.1.1.7,5.1.1.6,5.1.1.5,5.1.1.4,5.0.2.14,5.0.2.13,5.0.2.12,5.0.2.11,5.0.2.10

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK13792

Byte size of APAR:  11240

Date: 2006-02-13

Abstract:  Source code for JSP could be displayed instead of formatted output.

Description/symptom of problem:  

PK13792 resolves the following problem:

ERROR DESCRIPTION:                                              
Under some circumstances JSP source code can be displayed in the browser instead of an expected HTML response. 

This problem can be considered as a vulnerability exposure and only WebSphereŽ Application Server V5.0 and V5.1 on all platforms are affected. 

This fix also addresses the problem of garbage characters being returned with UTF-8.

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
Websphere Application Server users of
version 5.0 and 5.1.

PROBLEM DESCRIPTION:
Under some circumstances JSP source code can be displayed in the browser instead of an expected HTML response. 

RECOMMENDATION:
None


PROBLEM CONCLUSION:                                             
A specific JSP URL might expose JSP source code rather than JSP page.

With this fix, it should show the JSP page on all platforms.
This fix should be applied to both Base and Network Deployment. 




Directions to apply fix:  
NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note

Fix applies to Editions:
Release:
5.0  5.1
_x__  _x__ Application Server (Express or BASE)
___      Enterprise Edition (DD)
_x__  _x__ Network Deployment (ND)
___  ___ Edge Components
___  ___ Developers Edition
___  ___ Tools
     ___ WebSphere Business Integration Server Foundation (WBISF)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
__ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

The Update Installer for V5.0 does not have a maintenance directory.
It uses fixpacks and fixes as the location of the unpacked files.

1) Copy PKxxxxx.jar file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (PKxxxxx.jar file which was copied in the maintenance directory).
The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes directory.

7) Install the maintenance package.

8) Restart WebSphere



Directions to remove fix:  
NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX

Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (PKxxxxx.jar).

6) UnInstall maintenance package.

7) Restart WebSphere



Directions to re-apply fix:  
1) Shutdown WebSphere.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere.





Additional Information: