Security Bulletin: Security Vulnerabilities in IBM® Java SDK affect multiple IBM Rational products based on IBM Jazz technology July 2019 CPU

Summary

There are multiple vulnerabilities in IBM® SDK Java Technology Edition, Version 1.7 and 1.8 that are used by IBM Jazz Team Server affecting the following IBM Jazz Team Server based Applications: Collaborative Lifecycle Management (CLM), Rational DOORS Next Generation (RDNG), Rational Engineering Lifecycle Manager (RELM), Rational Team Concert (RTC), Rational Quality Manager (RQM), Rational Rhapsody Design Manager (Rhapsody DM), IBM Rhapsody Model Manager, and Rational Software Architect (RSA DM). These issues were disclosed as part of the IBM Java SDK updates in July 2019.

Vulnerability Details

CVEID: CVE-2019-2816 DESCRIPTION: An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded Networking component could allow an unauthenticated attacker to cause low confidentiality impact, low integrity impact, and no availability impact.
CVSS Base Score: 4.8
CVSS Temporal Score: See <https://exchange.xforce.ibmcloud.com/vulnerabilities/163878&gt; for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)

CVEID: CVE-2019-4473 DESCRIPTION: Multiple binaries in IBM SDK, Java Technology Edition on the AIX platform use insecure absolute RPATHs, which may facilitate code injection and privilege elevation by local users.
CVSS Base Score: 8.4
CVSS Temporal Score: See <https://exchange.xforce.ibmcloud.com/vulnerabilities/163984&gt; for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)

CVEID: CVE-2019-11771 DESCRIPTION: Eclipse OpenJ9 could allow a local attacker to gain elevated privileges on the system, caused by the inclusion of unused RPATHS in AIX builds. An attacker could exploit this vulnerability to inject code and gain elevated privileges on the system.
CVSS Base Score: 8.4
CVSS Temporal Score: See <https://exchange.xforce.ibmcloud.com/vulnerabilities/163989&gt; for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)

Affected Products and Versions

Rational Collaborative Lifecycle Management 6.0 - 6.0.6.1

Rational Quality Manager 6.0 - 6.0.6.1

Rational Team Concert 6.0 - 6.0.6.1

Rational DOORS Next Generation 6.0 - 6.0.6.1

Rational Engineering Lifecycle Manager 6.0 - 6.0.6.1

Rational Rhapsody Design Manager 6.0 - 6.0.6.1

IBM Rhapsody Model Manager 6.0.5 - 6.0.6.1

Rational Software Architect Design Manager 6.0 - 6.0.1

Remediation/Fixes

1. If your product is deployed on WebSphere Application Server (WAS) and your deployment does not use an Eclipse based client nor the RM Browser plugin, then it is sufficient to continue using the existing version of your IBM Rational product, and only upgrade the JRE in the WAS server.
2. For the below remediations, if you have a WAS deployment, then WAS must also be remediated, in addition to performing your product upgrades. Follow instructions at Security Bulletin: Multiple Vulnerabilities in IBM® Java SDK affect WebSphere Application Server July 2019 CPU to get the WAS remediation.
3. If you are deploying the Rational products to a WAS Liberty or a Tomcat Server, you will need to follow the instructions below to upgrade the JRE, and then must also configure to complete the upgrade process:

• Stop the server: Navigate to the Server directory in your Rational product installation path and run this script: server.shutdown
• Navigate to the server directory in your Rational product installation path, open**server.startup**_ _script using prefered text editor (e.g., Notepad for Windows or Vim Editor for Linux) and add one more option to the healthcenter parameter set:
  • Search parameter -Dcom.ibm.java.diagnostics.healthcenter.agent in server.startup script to find the line containing the health center parameter.
    NOTE: For some Rational Collaborative Lifecycle Management versions, _ -Dcom.ibm.java.diagnostics.healthcenter.agent_ parameter may not be found in the server.startup, in this case the update is not needed and you can start using your server.
    Windows:
    Comment out the line (where HEALTHCENTER_OPTS parameter located) by inserting "rem " at the beginning of the line:
    Before modification:
    set HEALTHCENTER_OPTS=-agentlib:healthcenter _ …
    After modification:_
    rem set HEALTHCENTER_OPTS=-agentlib:healthcenter …
    Linux:
    Comment out the line (where HEALTHCENTER_OPTS parameter located) by inserting "# " at the beginning of the line:
    Before modification:
    export HEALTHCENTER_OPTS="-agentlib:healthcenter _ …
    After modification:_
    # export HEALTHCENTER_OPTS="-agentlib:healthcenter …
• Start the server. Navigate to the Server directory in your Rational product installation path and run this script: _server.startup. _

STEPS TO APPLY THE REMEDIATION:

1. Optionally, upgrade your products to an Extended Maintenance Release version: 6.0.2 or 6.0.6. Or optionally, upgrade to the latest 6.0.6.1 version.

2. Optionally, apply the latest ifix for your installed version.

3. Obtain the latest Java JRE CPU update for the IBM Java SDK using the following information.

• For the 6.0.6 and 6.0.6.1 release: JRE 7.1.4.50****(<product>-JavaSE-JRE-7.1SR4FP50) orJRE 8.0.5.40****(<product>-JavaSE-JRE-8.0SR5FP40)
  • Rational Collaborative Lifecycle Management 6.0.6.1
• For the 6.0.2 release: JRE 7.1.4.50****(<product>-JavaSE-JRE-7.1SR4FP50)
  • Rational Collaborative Lifecycle Management 6.0.2

4. Upgrade your JRE following the instructions in the link below:
How to update the IBM SDK for Java of IBM Rational products based on version 3.0.1.6 or later of IBM’s Jazz technology

5. Navigate to the server directory in your Rational product installation path, and go to jre/lib/security path.

6. Optionally, If you have not performed a Licenses upgrade as described in the link below, please follow the instructions to complete the setup:

No IBM Rational trial, server, or client access licenses available after upgrading Java and/or listed products

Workarounds and Mitigations

None