Monday, March 25, 2019

IBM Security Bulletin: Multiple vulnerabilities in OpenSSL affect IBM Rational ClearCase (CVE-2018-0734, CVE-2018-5407)

OpenSSL vulnerabilities were disclosed on October 30 2018 and November 2 2018 by the OpenSSL Project. OpenSSL is used by IBM Rational ClearCase. IBM Rational ClearCase has addressed the applicable CVEs.

CVE(s): CVE-2018-0734, CVE-2018-5407

Affected product(s) and affected version(s):

IBM Rational ClearCase versions:

Not all deployments of Rational ClearCase use OpenSSL in a way that is affected by these vulnerabilities.

You are vulnerable if your use of Rational ClearCase includes any of these configurations:

  1. You use the base ClearCase/ClearQuest integration client on any platform, configured to use SSL to communicate with a ClearQuest server.
  2. You use the UCM/ClearQuest integration on UNIX/Linux clients, configured to use SSL to communicate with a ClearQuest server.
    Note: Windows clients using the UCM/ClearQuest integration are not vulnerable.
  3. On UNIX/Linux clients, you use the Change Management Integration (CMI), when configured to use SSL to communicate with the server.
    Note: Windows clients using the CMI integration are not vulnerable.
  4. You use ratlperl, ccperl, or cqperl to run your own perl scripts, and those scripts use SSL connections.

    Refer to the following reference URLs for remediation and additional vulnerability details:
    Source Bulletin: https://www-01.ibm.com/support/docview.wss?uid=ibm10875298
    X-Force Database: https://exchange.xforce.ibmcloud.com/vulnerabilities/152085
    X-Force Database: https://exchange.xforce.ibmcloud.com/vulnerabilities/152484

    The post IBM Security Bulletin: Multiple vulnerabilities in OpenSSL affect IBM Rational ClearCase (CVE-2018-0734, CVE-2018-5407) appeared first on IBM PSIRT Blog.

Version Status
9.0.1 through 9.0.1.5 Affected
9.0 through 9.0.0.6 Affected
8.0.1 through 8.0.1.19 Affected
8.0 through 8.0.0.21 Affected


from IBM Product Security Incident Response Team https://ift.tt/2V1OZiQ

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.