Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2019.1653
Security Vulnerability in IBM Java SDK affect IBM Rational Team Concert
10 May 2019
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: IBM Rational Team Concert
Publisher: IBM
Operating System: Windows
Linux variants
IBM i
Solaris
AIX
OS X
Impact/Access: Denial of Service -- Remote/Unauthenticated
Resolution: Patch/Upgrade
CVE Names: CVE-2019-2602
Reference: ASB-2019.0118
ESB-2019.1549
ESB-2019.1495
ESB-2019.1446
Original Bulletin:
http://www.ibm.com/support/docview.wss?uid=ibm10884054
- --------------------------BEGIN INCLUDED TEXT--------------------
Security Bulletin: Security Vulnerability in IBM(R) Java SDK affect IBM Rational
Team Concert Apr 2019 CPU
PSIRT; security
Security Bulletin
Summary
There is a security vulnerability in IBM(R) SDK Java Technology Edition, Version
1.7 and 1.8 that is used by Rational Team Concert (RTC). This issue was
disclosed as part of the IBM Java SDK updates in April 2019.
Vulnerability Details
CVEID: CVE-2019-2602
DESCRIPTION: An unspecified vulnerability in Oracle Java SE related to the Java
SE, Java SE Embedded Libraries component could allow an unauthenticated
attacker to cause a denial of service resulting in a high availability impact
using unknown attack vectors.
CVSS Base Score: 7.5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/
159698 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
Affected Products and Versions
Rational Collaborative Lifecycle Management 6.0 - 6.0.6.1
Rational Team Concert 6.0 - 6.0.6.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(R) Java
SDK affect WebSphere Application Server April 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:
o Stop the server: Navigate to the Server directory in your Ratonal product
installation path and run this script: server.shutdown
o 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 ...
o 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, 6.0.6 or 6.0.6.1.
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.
o For the 6.0.6 and 6.0.6.1 release: JRE 7.1.4.45(<product>
-JavaSE-JRE-7.1SR4FP45) or JRE 8.0.5.35(<product>-JavaSE-JRE-8.0SR5FP35)
- Rational Collaborative Lifecycle Management 6.0.6.1
o For the 6.0.2 release: JRE 7.1.4.45(<product>-JavaSE-JRE-7.1SR4FP45)
- 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
Important Note
IBM strongly suggests that all System z customers be subscribed to the System z
Security Portal to receive the latest critical System z security and integrity
service. If you are not subscribed, see the instructions on the System z
Security web site. Security and integrity APARs and associated fixes will be
posted to this portal. IBM suggests reviewing the CVSS scores and applying all
security or integrity fixes as soon as possible to minimize any potential risk.
Reference
Complete CVSS v3 Guide
On-line Calculator v3
Related Information
IBM Secure Engineering Web Portal
IBM Product Security Incident Response Blog
Change History
09 May 2019: Initial version published
*The CVSS Environment Score is customer environment specific and will
ultimately impact the Overall CVSS Score. Customers can evaluate the impact of
this vulnerability in their environments by accessing the links in the
Reference section of this Security Bulletin.
Disclaimer
According to the Forum of Incident Response and Security Teams (FIRST), the
Common Vulnerability Scoring System (CVSS) is an "industry open standard
designed to convey vulnerability severity and help to determine urgency and
priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY
OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF
ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
Cross reference information
Product Component Platform Version Edition
Rational Platform 6.0, 6.0.1, 6.0.2, 6.0.3,
Collaborative Independent 6.0.4, 6.0.5, 6.0.6,
Lifecycle Management 6.0.6.1
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
https://www.auscert.org.au/bulletins/
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQIVAwUBXNTmbmaOgq3Tt24GAQhrtg/+MAo/kfaEuUwJsbD+jh3CBEV2s2JK1cuH
DcWpYAAbDsc7Te/i1S9VS4phs4B3i2zu7VUiclmHivWes6OOXHv2lnv0HtkRhVgp
UrRzLykQCE2krSupRloiv3hdMAyRdUZLln3v1M7fJwbidYJlrc4Ri8MBFGoS6Q8q
PFzpsh5DHjZu0/8py9wpYAmDJz2Uieo9PSPJtG6wRnmPt8S0sH1misLahVU5FSjh
0XPvDQr0Pbw57R21LfmuJ7c25GSyhZcYuetk5TGS15spKJyOlECZWR9h+QHHYCN8
fFNq7NdEf4p2W2LJb2moe2A691U6pHQ+Wqj0umqHj7oA3VifVCFRKliAK0L2rynI
og87l28oKc9J2DLxKva8q/gBHNru96qiwdM6eAz7b+2DMshfn0ZPqldnWEchbsNJ
DkYizWHNmNLQJmE1evJTPwclsDzdLEH2MCXvZ6LukYTmygCwqluEdswMgzmJsTdM
O0JJFa9w1or8UVtpR5PiYsqNQAZfP7oTq+jMnyOHtCgSqdmtrb5qfW1NYeIYRVz/
VsWCrjNAZhpEG+5rbWwlFegVCsTycn/nEcIVfKw3Jrlee3gh1bxncuXbtXv1Vwgp
1xNrxOko7Jtd98AO1zuGzo8TW6uRvyoaZS+OJaJCvqYQrECHrhhyCYPjDfNt/vV1
m0oEJ7cNcoI=
=JNU6
-----END PGP SIGNATURE-----