Fixes are available
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
In rare cases, when WebSphere Application Server receives application response data prior to the application sending out its request, the response data will be read into the same buffer as the change cipher spec packet, which causes it to never make it to the JSSE layer. If a CBC-mode cipher suite is in use, this will cause decryption to fail with a "Bad record MAC" error reported by JSSE.
Local fix
use a stream cipher or ensure that all application response data arrives after the application request is sent
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Version * * 7.0, 8.0, 8.5 and 8.5.5 Full Profile and * * Liberty Profile 8.5.5 users of the SSL * * Channel * **************************************************************** * PROBLEM DESCRIPTION: Request fails due to response data * * being lost on an SSL outbound * * connection. * **************************************************************** * RECOMMENDATION: * **************************************************************** During an outbound connection, the SSL Channel could read the end of the handshake and the beginning of the request data. In this case, the SSL Channel would disregard the already read request data. This could cause an exception while decrypting the request data. An example of the exception which can occur is: [9/17/15 14:06:17:238 CDT] 000012b7 SystemOut O WebContainer : 1, fatal error: 20: bad record MAC javax.crypto.BadPaddingException: bad record MAC
Problem conclusion
The SSL Channel was modified to correctly decrypt all application data. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.41, 8.0.0.12, and 8.5.5.9. 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
PI48725
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-09-14
Closed date
2015-11-13
Last modified date
2016-02-15
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
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022