Fixes are available
PM16014; 7.0.0.9: Potential security exposure with JAX-WS WS-Security runtime
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
When a general custom property is specified in a WS-Security binding, the WS-Security JAX-WS runtime may not behave as expected with regards to that custom property. For example, consider the following custom property specified as a general Outbound Custom property in a general binding: com.ibm.wsspi.wssecurity.config.request.setMustUnderstand When an application uses the general binding, the WS-Security runtime uses the default setting instead of the user's specified value.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V7.0 users * * of WS-Security enabled JAX-WS web services * * applications * **************************************************************** * PROBLEM DESCRIPTION: WS-Security JAX-WS general custom * * properties may not behave as expected * **************************************************************** * RECOMMENDATION: Install a fixpack that contains this APAR * **************************************************************** When a general custom property is specified in a WS-Security JAX-WS custom binding, the WS-Security runtime may not behave as expected with regards to that custom property. There is more than one manifestation of this problem: * If the property is specified in a general binding, it will not be effective at all. * If the property is specified in a general binding, it will only be effective if the general binding itself is attached to the application. When using an application specific binding, the setting of a custom property in the default general binding is not detected.
Problem conclusion
The WS-Security JAX-WS runtime is not merging the properties from the default general binding with the ones from the application specific binding. Also, the custom property setting has to be inspected in three places: initialization of the application specific binding, initialization of the default general binding, and merging of the two at runtime, which causes too much room for error when adding new custom properties. The runtime is updated to first set up the general custom property hierarchy properly in the following priority order: 1) Inbound/Outbound (Application specific binding) 2) Inbound and Outbound (Application specific binding) 3) Inbound/Outbound (General binding) 4) Inbound and Outbound (General binding) This behavior is prescribed in the information center: http://publib.boulder.ibm.com/infocenter/wasinfo/fep/topic/com.i bm.websphere.nd.multiplatform.doc/info/ae/ae/uwbs_wsscustomprop. html The runtime is also updated to require only a single inspection for a custom property in the merged custom property list to prevent similar errors in the future. Properties that are affected include: com.ibm.wsspi.wssecurity.config.disableWSSIfApplicationSecurityD isabled com.ibm.wsspi.wssecurity.config.response.forceMustUnderstandEqua lsOne com.ibm.wsspi.wssecurity.config.request.setMustUnderstand com.ibm.wsspi.wssecurity.consumer.checkOperationLevelPolicies The WS-Security general custom properties are accessed as follows: (bindingName)->WS-Security->Custom properties The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.13. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM07663
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-16
Closed date
2010-04-26
Last modified date
2010-04-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
24 October 2021