Fixes are available
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
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
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
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
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
When using %{SSL_CIPHER}e in logformat for access log some cipers are not logged resulting a null "-" in access log. Based on access log it looks like :%{SSL_CIPHER}e is not logged when the TLS protocol is TLSV12 but logged when TLSV11 or 10. More correctly, TLSV1.2 does not appear to log when the CIPHER is TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA. Other ECDHE ciphers may cause same issue. #cipher logs as expected when these are commented out SSLCipherSpec TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA SSLCipherSpec TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA SSLCipherSpec TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 SSLCipherSpec TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 SSLCipherSpec TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 SSLCipherSpec TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 SSLCipherSpec TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA #these ciphers do print if used SSLCipherSpec ALL TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA SSLCipherSpec ALL SSL_RSA_WITH_3DES_EDE_CBC_SHA SSL_RSA_WITH_RC4_128_SHA SSL_RSA_WITH_RC4_128_MD5
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users logging TLSv12 ciphers through the * * use of the SSL_CIPHER or HTTPS_CIPHER * * environment variable are affected. * **************************************************************** * PROBLEM DESCRIPTION: The SSL_CIPHER/HTTPS_CIPHER * * environment variables are empty when * * some TLSv12 ciphers are used. * **************************************************************** * RECOMMENDATION: Apply this fix if the environment * * variables are being used to log the cipher * * used. * **************************************************************** The SSL_CIPHER or HTTPS_CIPHER environment variable is used to log the HTTPS cipher being used within a request, e.g. CustomLog "%{SSL_CIPHER}e" ssl_cipher_log For some TLSv12 ciphers (most notably, all elliptic-curve ciphers), this value was being logged as empty.
Problem conclusion
The issue with TLSv12 ciphers not being logged in SSL_CIPHER/HTTPS_CIPHER has been resolved. This fix is targeted for IBM HTTP Server fix packs: - 8.0.0.11 - 8.5.5.6 7.0 is not affected.
Temporary fix
Comments
APAR Information
APAR number
PI32841
Reported component name
IBM HTTP SERVER
Reported component ID
5724J0801
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-01-15
Closed date
2015-01-29
Last modified date
2015-03-05
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
IBM HTTP SERVER
Fixed component ID
5724J0801
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
07 September 2022