Lucene search

K
ibmIBMF6B12E71E2DB2799F9D676203B307109C582565C2D18CEABC3ED26E527BD348D
HistoryApr 09, 2021 - 6:07 a.m.

Security Bulletin: A vulnerability exists in the IBM® SDK, Java™ Technology Edition affecting IBM Tivoli Network Configuration Manager (CVE-2020-14803, CVE-2020-27221).

2021-04-0906:07:03
www.ibm.com
23
ibm
tivoli
network configuration manager
java
vulnerability
update
version 8
cve-2020-14803
cve-2020-27221
remediation
aix
linux
zlinux.

EPSS

0.004

Percentile

75.0%

Summary

A vulnerability exists in IBM® SDK Java™ Technology Edition, Version 8, which is used by IBM Tivoli Network Configuration Manager IP Edition v6.4.2, which was disclosed in the Oracle January 2021 Critical Patch Update.

Vulnerability Details

Refer to the security bulletin(s) listed in the Remediation/Fixes section

Affected Products and Versions

Affected Product(s) Version(s)
ITNCM 6.4.1
ITNCM 6.4.2

Remediation/Fixes

Note that only standalone worker servers and compliance servers (i.e. those which are not co-located on the same machine as a presentation server) need to have their JRE updated. To update the Java Runtime Environment (JRE), complete the following steps.

1. Locate the appropriate IBM JRE for your operating system on the IBM Fix Central website.

AIX: IBM Java 8.0.6.26 for AIX

Linux: IBMJava 8.0.6.26 for 64-bit Linux

zLinux: IBM Java 8.0.6.26 for Linux for z/OS

2. Download version 8.0.6.26 in archive, rather than binary, form and install it.

3. Back up the directory $NCMHOME/jre.

4. Stop all running processes of the compliance or worker server by using the “itncm.sh stop” command.

5. Delete the contents of the $NCMHOME/jre/bin and $NCMHOME/jre/lib directory.

6. Copy the contents of the bin and lib directories from the JRE that you installed in step 2 to $NCMHOME/jre/bin and $NCHOME/jre/lib, respectively.

7. Restart the compliance or worker server by using the “itncm.sh start” command.

To roll back to the previous Netcool Configuration Manager compliance or worker server JRE, restore the backup that you made in step 3. Perform the rollback, then perform steps 4 to 7 again.

Workarounds and Mitigations

None