Security Bulletin: A vulnerabbility exists in IBM® SDK, Java™ Technology Edition affecting IBM Tivoli Netcool Configuration Manager (CVE-2021-2163).

Summary

A vulnerability exists in IBM® SDK Java™ Technology Edition, Version 8, which is used by IBM Tivoli Netcool Configuration Manager v6.4.2, which was disclosed in the Oracle April 2021 Critical Patch Update, but deferred until the release associated with the August 2022 Update.

Vulnerability Details

CVEID:CVE-2021-2163
**DESCRIPTION:**An unspecified vulnerability in Java SE related to the Libraries component could allow an unauthenticated attacker to cause no confidentiality impact, high integrity impact, and no availability impact.
CVSS Base score: 5.3
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/200292 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N)

Affected Products and Versions

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.7.15 for AIX
• Linux: IBM Java 8.0.7.15 for 64-bit Linux
• zLinux: IBM Java 8.0.7.15 for Linux zSeries

2. Download version 8.0.7.15 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