7.1 High
CVSS2
Access Vector
NETWORK
Access Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
COMPLETE
AV:N/AC:M/Au:N/C:N/I:N/A:C
IBM Security Directory Server is affected by a problem related to the SSL implementation which, under very specific conditions, can cause CPU utilization to rapidly increase.
CVE ID:
CVE-2014-0963
DESCRIPTION:
IBM Security Directory Server 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 that causes a single thread to begin looping. If this happens multiple times, more threads will begin to loop and an increase in CPU utilization will be seen. This increase could ultimately result in CPU exhaustion and unresponsiveness of the IBM Security Directory Server 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 IBM Security Directory Server instances.
CVSS Base Score: 7.1
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/92844 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:N/I:N/A:C)
All versions of IBM Security Directory Server (ISDS): 6.1.0, 6.2.0, 6.3.0, 6.3.1
IBM has provided patches for all affected versions. Please install the GSKit package included with the patch.
Affected Version | GSKit Release | Fix |
---|---|---|
ISDS 6.1.0 | 7.0.4.50 | 6.1.0.61-ISS-ITDS |
ISDS 6.2.0 | 7.0.4.50 | 6.2.0.36-ISS-ITDS |
ISDS 6.3.0 | 8.0.50.20 | 6.3.0.30-ISS-ITDS |
ISDS 6.3.1 | 8.0.50.20 | 6.3.1.2-ISS-ISDS |
Monitor CPU utilization of your Program Name instances. If utilization becomes abnormally high, stop and restart the affected instance.