Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
No replies
gpfs@us.ibm.com
gpfs@us.ibm.com
217 Posts
ACCEPTED ANSWER

Pinned topic Security Bulletin: GPFS V3.5 for Windows is affected by vulnerabilities in OpenSSL (CVE-2014-0160 and CVE-2014-0076)

‏2014-04-14T12:38:12Z |

See the complete bulletin here -  http://www-01.ibm.com/support/docview.wss?uid=isg3T1020683

 

Affected Products and Versions

GPFS for Windows V3.5

Remediation/Fixes

GPFS for Windows V3.4

This version of GPFS uses OpenSSH 0.9.8y which is not affected by this vulnerability.

 

GPFS for Windows V3.5

 

If using GPFS on Windows V3.5.0.1, please upgrade to the latest 3.5 PTF level immediately.

For GPFS on Windows V3.5.0.11 or later, the OpenSSL libraries which are linked in OpenSSH for GPFS on Windows, have been upgraded to 1.0.1g. This updated OpenSSH for GPFS on Windows package is available for download from FixCentral http://www-933.ibm.com/support/fixcentral/ :


  • 1. Download the GPFS 3.5.0.17 update package into any directory on your system.

    2. Extract the contents of the ZIP archive so that the .msi file it includes is directly accessible to your system.
    3. Follow the instructions in the README included in the update package in order to install the OpenSSH msi package.

 

If GPFS multiclustering is configured on Windows nodes, upgrade any OpenSSL package that may have been installed. If using OpenSSL from Shining Light Productions (https://slproweb.com/products/Win32OpenSSL.html), get the latest version of OpenSSL 1.0.1g which is available on their website.


Actions that should be taken:

1.The following can be done on a small group of nodes at each time (ensuring that quorum is maintained) to maintain file system availability:

  • a. Stop GPFS on the node
    b. Install the version of OpenSSL which contains the fix
    c. Restart GPFS on the node

2. Additional instructions are needed for CVE-2014-0160. The following should be done only when all nodes, across the multiple clusters, are running with at OpenSSL 1.0.1g level (i.e., when the above steps are completed):
  • a. Change the security keys used for secure communications. Refer to the Advanced Administration Guide, Chapter 1: Accessing GPFS file systems from other GPFS clusters", "Changing security keys" section . The steps should be taken up to, and including the procedure to ensure that the old key is no longer accepted

    b. If SSH is used to execute remote GPFS commands, then the SSH host keys must also be changed

    c. If SSH is used to execute remote GPFS commands, then SSH user keys/passwords must also be changed.


Warning: Your environment may require additional fixes for other products, including non-IBM products. Please replace the SSL certificates and reset the user credentials after applying the necessary fixes to your environment.