Security Bulletin: Rational Developer for System z CPU utilization (CVE-2014-0963)

Summary

IBM Rational Developer for System z is affected by a problem related to the SSL implementation which, under very specific conditions, can cause CPU utilization to rapidly increase.

Vulnerability Details

| Subscribe to My Notifications to be notified of important product support alerts like this.

• Follow this link for more information (requires login with your IBM ID)
  —|—

CVE ID: CVE-2014-0963

**Description:**Rational Developer for System z is affected by a problem with the handling of certain SSL messages. The TLS implementation can, under very specific conditions, cause CPU utilization to rapidly increase. The situation occurs only in a certain error case. If this error case happens multiple times, an increase in CPU utilization will be seen. This increase could ultimately result in CPU exhaustion and unresponsiveness of the Rational Developer for System z and other software running on the affected system.

This issue can affect the availability of the system, but does not impact system confidentiality or integrity. This vulnerability can be remotely exploited, authentication is not required and the exploit is moderately complex.

To determine if your systems are being affected by this issue, you can monitor the CPU utilization for Rational Developer for System z instances.

CVSS Base Score: 7.1
CVSS Temporal Score: See <https://exchange.xforce.ibmcloud.com/vulnerabilities/92844&gt; for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:N/I:N/A:C)

Affected Products and Versions

Rational Developer for System z Version 9.0.1.1, 9.0.1.1 ifix 1, 9.0.1.2

Remediation/Fixes

IBM has provided patches for all affected versions.

Follow the installation instructions in the README files included with the patch.

The fix can be obtained at the following location: Rational Developer for System z 9.0.1.0, All platforms

Workarounds and Mitigations

Monitor CPU utilization of your Program Name instances. If utilization becomes abnormally high, stop and restart the affected instance.