Security Bulletin: TLS padding vulnerability affects Tivoli Access Manager for e-business and IBM Security Access Manager for Web (CVE-2014-8730)

Workarounds and Mitigations

The following steps describe how to mitigate this vulnerability for the affected releases.

Security patches have been provided for all versions of IBM Tivoli Access Manager for e-business (TAMeb) and IBM Security Manager for Web (ISAM for Web). The mitigations for the TLS padding vulnerability require that these patches be installed first. Please read the security bulletins provided in the table below for your product version for instructions on obtaining and applying the necessary security patches.

Set GSK_STRICTCHECK_CBCPADBYTES=GSK_TRUE in the server process environment.

Mitigation for all ISAM for Web 7.0 and 8.0 appliance versions

1. Select 'Secure Web Settings -> Reverse Proxy' from the menu bar;
2. Select the WebSEAL instance;
3. Select 'Manage -> Configuration -> Edit Configuration File' from the menu
4. In the [ssl] stanza, add the bold lines below to the following two sections.

# Specify any additional GSKit attributes which should be used when
# initializing an SSL connection with the client. A complete list of
# the available attributes is included in the GSKit SSL API documentation.
#
# The configuration entry may be specified multiple times, one for each
# GSKit attribute. The entry should be of the format:
# gsk-attr-name = <type>:<id>:<value>
#
# - where <type> is one of 'enum', 'string', 'number'
# and <id> corresponds to the identity associated with a GSKit attribute
# (e.g. GSK_HTTP_PROXY_SERVER_NAME = 225)
#
# An example configuration could be:
# gsk-attr-name = string:225:proxy.ibm.com
gsk-attr-name = enum:471:1


# Specify any additional GSKit attributes which should be used when
# initializing an SSL connection with a junctioned server. A complete list of
# the available attributes is included in the GSKit SSL API documentation.
#
# The configuration entry may be specified multiple times, one for each
# GSKit attribute. The entry should be of the format:
# jct-gsk-attr-name = <type>:<id>:<value>
#
# - where <type> is one of 'enum', 'string', 'number'
# and <id> corresponds to the identity associated with a GSKit attribute
# (e.g. GSK_HTTP_PROXY_SERVER_NAME = 225)
#
# An example configuration could be:
# jct-gsk-attr-name = string:225:proxy.ibm.com
jct-gsk-attr-name = enum:471:1