Readme File for IBM® Spectrum Symphony 7.3.1 Interim Fix 600994

Readme file for: IBM Spectrum Symphony
Product release: 7.3.1
Fix ID: sym-7.3.1-build600994-jpmc

Publication date: February 10, 2022

 

This interim fix upgrade log4j 2.x to version 2.17.1 to resolve security vulnerability issues CVE-2021-44228, CVE-2021-44832, CVE-2021-45046, and CVE-2021-45105 for IBM Spectrum Symphony 7.3.1 on Linux.

 

Contents

1.      List of fixes

2.      Download location 

3.      Product or components affected

4.      Installation and configuration

5.      Uninstallation

6.      List of files

7.      Product notifications 

8.      Copyright and trademark information

1.     List of fixes

APAR: P104557

2.     Download location

Download interim fix 600994 from the following location: https://www.ibm.com/support/fixcentral

3.     Product or components affected

Component name, Platform, Fix ID:

ELK, Linux x86_64, sym-7.3.1-build600994-jpmc

4.     Installation and configuration

Follow these instructions to download and install this interim fix on the hosts in your cluster.

System requirements

Linux x86_64

Installation

a.       Log on to the primary host as the cluster administrator:

$ egosh user logon -u Admin -x Admin

b.     Stop the Elastic Search related services as follows:

1)     Run egosh service stop elk-shipper.

Verify that the elk-shipper service is in DEFINED state:  
egosh service list -ll | grep elk-shipper | grep DEFINED

2)     Run egosh service stop elk-indexer.

Verify that the elk-indexer service is in DEFINED state.

3)     Run egosh service stop elk-elasticsearch elk-elasticsearch-master elk-elasticsearch-data.

Verify that all these elk-elasticsearch services are in DEFINED state.

4)     Run egosh service stop elk-manager.

Verify that the elk-manager service is in DEFINED state.

c.       On each management host, create a directory (for example, /symfixes) and download the egoelastic-1.4.4.0_x86_64_build600994.tar.gz file to the directory.

d.       Run the egoinstallfixes command to install the egoelastic-1.4.4.0_x86_64_build600994.tar.gz file:

$ egoinstallfixes /symfixes/egoelastic-1.4.4.0_x86_64_build600994.tar.gz

Important: Running the egoinstallfixes command automatically backs up the current binary files to a fix backup directory. For recovery purposes of the original file, do not delete this backup directory. For more information on using this command, see the egoinstallfixes command reference.

e.     Run the pversions command to verify the installation:

$ pversions -b 600994

f.    If required, restart the Elastic Stack related services.

5.     Uninstallation

If required, follow the instructions to uninstall this interim fix from the hosts in your cluster.

a.       Log on to the primary host as the cluster administrator:

$ egosh user logon -u Admin -x Admin

b.    Stop the Elastic Stack related services as described in step b of the “Installation” section.

c.    On each management host, roll back this interim fix:

$ egoinstallfixes -r 600994

d.   If required, restart the Elastic Stack related services. 

6.     List of files 

integration/elk/1.4.4/elasticsearch-7.8.1/lib/log4j-api-2.17.1.jar

integration/elk/1.4.4/elasticsearch-7.8.1/lib/log4j-core-2.17.1.jar

integration/elk/1.4.4/logstash-7.8.1/logstash-core/lib/jars/log4j-api-2.17.1.jar

integration/elk/1.4.4/logstash-7.8.1/logstash-core/lib/jars/log4j-core-2.17.1.jar

integration/elk/1.4.4/logstash-7.8.1/logstash-core/lib/jars/log4j-slf4j-impl-2.17.1.jar

integration/elk/1.4.4/logstash-7.8.1/vendor/bundle/jruby/2.5.0/gems/logstash-input-azure_event_hubs-1.2.2/vendor/jar-dependencies/org/apache/logging/log4j/log4j-api/2.17.1/log4j-api-2.17.1.jar

integration/elk/1.4.4/logstash-7.8.1/vendor/bundle/jruby/2.5.0/gems/logstash-input-azure_event_hubs-1.2.2/vendor/jar-dependencies/org/apache/logging/log4j/log4j-slf4j-impl/2.17.1/log4j-slf4j-impl-2.17.1.jar

integration/elk/1.4.4/logstash-7.8.1/vendor/bundle/jruby/2.5.0/gems/logstash-input-beats-6.0.11-java/vendor/jar-dependencies/org/apache/logging/log4j/log4j-api/2.17.1/log4j-api-2.17.1.jar

integration/elk/1.4.4/logstash-7.8.1/vendor/bundle/jruby/2.5.0/gems/logstash-input-http-3.3.5-java/vendor/jar-dependencies/org/apache/logging/log4j/log4j-api/2.17.1/log4j-api-2.17.1.jar

integration/elk/1.4.4/logstash-7.8.1/vendor/bundle/jruby/2.5.0/gems/logstash-input-tcp-6.0.6-java/vendor/jar-dependencies/org/logstash/inputs/logstash-input-tcp/6.0.6/logstash-input-tcp-6.0.6.jar

integration/elk/1.4.4/logstash-7.8.1/vendor/bundle/jruby/2.5.0/gems/logstash-input-http-3.3.5-java/lib/logstash-input-http_jars.rb

integration/elk/1.4.4/logstash-7.8.1/vendor/bundle/jruby/2.5.0/gems/logstash-input-beats-6.0.11-java/lib/logstash-input-beats_jars.rb

integration/elk/1.4.4/logstash-7.8.1/vendor/bundle/jruby/2.5.0/gems/logstash-input-azure_event_hubs-1.2.2/lib/logstash-input-azure_event_hubs.rb

 

7.     Product notifications

To receive information about product solution and patch updates automatically, subscribe to product notifications on the My Notifications page http://www.ibm.com/support/mynotifications/ on the IBM Support website (http://support.ibm.com). You can edit your subscription settings to choose the types of information you want to get notification about, for example, security bulletins, fixes, troubleshooting, and product enhancements or documentation changes. 

8.     Copyright and trademark information 

© Copyright IBM Corporation 2022

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM®, the IBM logo and ibm.com® are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml