Readme File for IBM® Spectrum Symphony 7.2.0.2 Interim Fix 600934

Readme File for: IBM Spectrum Symphony

Product Release: 7.2.0.2

Update Name: Interim Fix 600934

Fix ID: sym-7.2.0.2-build600934

Publication Date: January 9, 2022

 

This interim fix upgrades 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.2.0.2 on Linux.

Contents

1. List of fixes

2. Download location

3. Product and 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: P104504

2.    Download location

Download interim fix 600934 from the following location: https://www.ibm.com/eserver/support/fixes/

3.    Product and components affected

Component name, Platform, Fix ID:

ELK, GUI, KC, Linux x86_64, sym-7.2.0.2-build600934

4.    Installation and configuration

Follow the instructions in this section to download and install this interim fix to your cluster.

System requirements

Linux x86_64

Installation

a.     Log on to the primary host in the cluster as the cluster administrator and stop the WEBGUI service:

> egosh user logon -u Admin -x Admin

> egosh service stop WEBGUI

b.   Stop the Elastic Stack related services:

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.     For recovery purposes, log on to each management host in your cluster as the cluster administrator and back up the following files:

cd $EGO_TOP/

tar -cvf backup_old_600934.tar integration/elk/1.4/elasticsearch-5.4.2/lib/log4j-1.2-api-2.*.jar

tar -uvf backup_old_600934.tar integration/elk/1.4/elasticsearch-5.4.2/lib/log4j-api-2.*.jar

tar -uvf backup_old_600934.tar integration/elk/1.4/elasticsearch-5.4.2/lib/log4j-core-2.*.jar

tar -uvf backup_old_600934.tar integration/elk/1.4/logstash-5.4.2/logstash-core/lib/org/apache/logging/log4j/log4j-core/2.6.2/log4j-core-2.*.jar

tar -uvf backup_old_600934.tar integration/elk/1.4/logstash-5.4.2/logstash-core/lib/org/apache/logging/log4j/log4j-api/2.6.2/log4j-api-2.*.jar

tar -uvf backup_old_600934.tar wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-core-2.*.jar

tar -uvf backup_old_600934.tar wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-slf4j-impl-2.*.jar

tar -uvf backup_old_600934.tar wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-1.2-api-2.*.jar

tar -uvf backup_old_600934.tar wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-api-2.*.jar

tar -uvf backup_old_600934.tar integration/elk/1.4/logstash-5.4.2/logstash-core/lib/logstash-core_jars.rb

tar -uvf backup_old_600934.tar integration/elk/1.4/logstash-5.4.2/logstash-core/gemspec_jars.rb

d.     Remove the old log4j 2.x jar files:

rm -rf $EGO_TOP/integration/elk/1.4/elasticsearch-5.4.2/lib/log4j-1.2-api-2.*.jar 

rm -rf $EGO_TOP/integration/elk/1.4/elasticsearch-5.4.2/lib/log4j-api-2.*.jar 

rm -rf $EGO_TOP/integration/elk/1.4/elasticsearch-5.4.2/lib/log4j-core-2.*.jar 

rm -rf $EGO_TOP/integration/elk/1.4/logstash-5.4.2/logstash-core/lib/org/apache/logging/log4j/log4j-core/2.6.2/log4j-core-2.*.jar 

rm -rf $EGO_TOP/integration/elk/1.4/logstash-5.4.2/logstash-core/lib/org/apache/logging/log4j/log4j-api/2.6.2/log4j-api-2.*.jar 

rm -rf $EGO_TOP/wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-core-2.*.jar 

rm -rf $EGO_TOP/wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-slf4j-impl-2.*.jar 

rm -rf $EGO_TOP/wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-1.2-api-2.*.jar 

rm -rf $EGO_TOP/wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-api-2.*.jar

e.   Download the sym-7.2.0.2_x86_64_build600934.tar.gz package and install the fix:

> tar zxfo sym-7.2.0.2_x86_64_build600934.tar.gz -C $EGO_TOP/

f.     Delete all subdirectories and files from the following directories:

> rm -rf $EGO_TOP/gui/work/*

> rm -rf $EGO_TOP/gui/workarea/*

(Optional) > rm -rf $WLP_OUTPUT_DIR/webgui_hostname/gui/workarea/*

g.     Clear your browser cache.

h.   Edit the $EGO_TOP/integration/elk/1.4/logstash-5.4.2/logstash-core/lib/logstash-core_jars.rb file to use log4j*2.17.1 and remove the old version as follows:

require 'org/apache/logging/log4j/log4j-core/2.17.1/log4j-core-2.17.1.jar'

require 'org/apache/logging/log4j/log4j-api/2.17.1/log4j-api-2.17.1.jar'

require_jar( 'org.apache.logging.log4j', 'log4j-core', '2.17.1' )

require_jar( 'org.apache.logging.log4j', 'log4j-api', '2.17.1' )

i.   Edit the $EGO_TOP/integration/elk/1.4/logstash-5.4.2/logstash-core/gemspec_jars.rb file to use log4j*2.17.1 and remove the old version as follows:

gem.requirements << "jar org.apache.logging.log4j:log4j-api, 2.17.1"

gem.requirements << "jar org.apache.logging.log4j:log4j-core, 2.17.1"

j.    From the primary host, start the WEBGUI service:

> egosh service start WEBGUI

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

5.    Uninstallation

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

a.     Log on to the primary host in the cluster as the cluster administrator and stop the WEBGUI service:

> egosh user logon -u Admin -x Admin

> egosh service stop WEBGUI

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

c.   Remove the installed fix.

rm $EGO_TOP/integration/elk/1.4/elasticsearch-5.4.2/lib/log4j-1.2-api-2.*.jar

rm $EGO_TOP/integration/elk/1.4/elasticsearch-5.4.2/lib/log4j-api-2.*.jar

rm $EGO_TOP/integration/elk/1.4/elasticsearch-5.4.2/lib/log4j-core-2.*.jar

rm $EGO_TOP/integration/elk/1.4/logstash-5.4.2/logstash-core/lib/org/apache/logging/log4j/log4j-api/2.17.1/log4j-api-2.*.jar

rm $EGO_TOP/integration/elk/1.4/logstash-5.4.2/logstash-core/lib/org/apache/logging/log4j/log4j-core/2.17.1/log4j-core-2.*.jar

rm $EGO_TOP/wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-1.2-api-2.*.jar

rm $EGO_TOP/wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-api-2.*.jar

rm $EGO_TOP/wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-core-2.*.jar

rm $EGO_TOP/wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-slf4j-impl-2.*.jar

d.     Log on to each management host in your cluster as the cluster administrator and restore your backup for the following files:

cd $EGO_TOP

tar -xvf backup_old_600934.tar

e.     Delete all subdirectories and files from the following directories:

> rm -rf $EGO_TOP/gui/work/*

> rm -rf $EGO_TOP/gui/workarea/*

(Optional) > rm -rf $WLP_OUTPUT_DIR/webgui_hostname/gui/workarea/*

f.     Clear your browser cache.

g.     From the primary host, start the WEBGUI service:

> egosh service start WEBGUI

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

6.    List of files

integration/elk/1.4/elasticsearch-5.4.2/lib/log4j-1.2-api-2.17.1.jar

integration/elk/1.4/elasticsearch-5.4.2/lib/log4j-api-2.17.1.jar

integration/elk/1.4/elasticsearch-5.4.2/lib/log4j-core-2.17.1.jar

integration/elk/1.4/logstash-5.4.2/logstash-core/lib/org/apache/logging/log4j/log4j-api/2.17.1/log4j-api-2.17.1.jar

integration/elk/1.4/logstash-5.4.2/logstash-core/lib/org/apache/logging/log4j/log4j-core/2.17.1/log4j-core-2.17.1.jar

wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-1.2-api-2.17.1.jar

wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-api-2.17.1.jar

wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-core-2.17.1.jar

wlp/usr/servers/gui/apps/kc/1.5.1.5/kc/WEB-INF/lib/log4j-slf4j-impl-2.17.1.jar

7.    Product notification

To receive information about product solution and patch updates automatically, subscribe to product notifications on the My Notifications page 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.