Security Bulletin: Vulnerabilities in OpenSSL including Logjam affect IBM InfoSphere Master Data Management (CVE-2015-4000)

Summary

OpenSSL vulnerabilities were disclosed on June 11, 2015 by the OpenSSL Project. This includes Logjam Attack on TLS connections using the Diffie-Hellman (DH) key exchange protocol (CVE-2015-4000). OpenSSL is used by IBM InfoSphere Master Data Management. IBM InfoSphere Master Data Management has addressed the applicable CVEs.

Vulnerability Details

CVEID: CVE-2015-4000 DESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as “Logjam”.
CVSS Base Score: 4.3
CVSS Temporal Score: See<https://exchange.xforce.ibmcloud.com/vulnerabilities/103294&gt; for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)

Affected Products and Versions

These vulnerabilities are known to affect the following offerings:

IBM Initiate Master Data Service versions 9.5, 9.7, 10.0, 10.1 (impacts Master Data Engine component, Message Brokers component and Enterprise Integrator Toolkit component)

IBM Initiate Master Data Service Patient Hub versions 9.5, 9.7 (impacts Master Data Engine component, Message Brokers component and Enterprise Integrator Toolkit component)

IBM Initiate Master Data Service Provider Hub versions 9.5, 9.7 (impacts Master Data Engine component, Message Brokers component and Enterprise Integrator Toolkit component)

IBM InfoSphere Master Data Management Patient Hub version 10.0 (impacts Master Data Engine component, Message Brokers component and Enterprise Integrator Toolkit component)

IBM InfoSphere Master Data Management Provider Hub version 10.0 (impacts Master Data Engine component, Message Brokers component and Enterprise Integrator Toolkit component)

IBM InfoSphere Master Data Management Standard/Advanced Edition version 11.0 (impacts Message Brokers component and Enterprise Integrator Toolkit component)

IBM InfoSphere Master Data Management Standard/Advanced Edition version 11.3 (impacts Message Brokers component)

IBM InfoSphere Master Data Management Standard/Advanced Edition version 11.4 (impacts Message Brokers component)

Remediation/Fixes

The recommended solution is to apply the fix as soon as practical. Please see below for information on the fixes available.

9.5

| None| 9.5.071215
IBM Initiate Master Data Service Patient Hub|

9.5

| None| 9.5.071215
IBM Initiate Master Data Service Provider Hub|

9.5

| None| 9.5.071215
IBM Initiate Master Data Service |

9.7

| None| 9.7.071215
IBM Initiate Master Data Service Patient Hub |

9.7

| None| 9.7.071215
IBM Initiate Master Data Service Provider Hub|

9.7

| None| 9.7.071215
IBM Initiate Master Data Service|

10.0

| None| 10.0.071215
IBM InfoSphere Master Data Management Patient Hub |

10.0

| None| 10.0.071215
IBM InfoSphere Master Data Management Provider Hub|

10.0

| None| 10.0.071215
IBM Initiate Master Data Service|

10.1

| None| 10.1.071215
IBM InfoSphere Master Data Management Standard/Advanced Edition|

11.0

| None| 11.0-FP3-IF3
IBM InfoSphere Master Data Management Standard/Advanced Edition|

11.3

| None| 11.3-FP3-IF1
IBM InfoSphere Master Data Management Standard/Advanced Edition|

11.4

| None| 11.4-FP3-IF1

As the length of the server key size are increased, the amount of CPU required for full TLS/SSL handshake can significantly increase. Please carefully test and assess the impact to your CPU requirements to ensure sufficient CPU resources, otherwise the system availability may be impacted.

You should verify applying this configuration change does not cause any compatibility issues. If you change the default setting after applying the fix, you will expose yourself to the attack described above. IBM recommends that you review your entire environment to identify other areas where you have enabled the Diffie-Hellman key-exchange protocol used in TLS and take appropriate mitigation and remediation actions.

Workarounds and Mitigations

None known.