copyright | disclaimer | privacy | contact  
Australia's Leading Computer Emergency Response Team
 
Search this site

 
On this site

 > HOME
 > About AusCERT
 > Membership
 > Contact Us
 > PKI Services
 > Publications
 > Sec. Bulletins
 > Conferences
 > News & Media
 > Services
 > Web Log
 > Site Map
 > Site Help
 > Member login





 

ESB-2016.0452.2 - UPDATE [Win][Linux][HP-UX][Solaris][AIX] IBM Rational License Key Server: Multiple vulnerabilities

Date: 24 February 2016
References: ESB-2016.0046  ESB-2016.0047  ESB-2016.0049  ASB-2016.0004  ESB-2016.0413  ESB-2016.0430  

Click here for printable version
Click here for PGP verifiable version
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                              ESB-2016.0452.2
 Security Bulletin: Multiple Security Vulnerabilities in IBM Java Runtime
     affect IBM RLKS Administration and Reporting Tool Admin and Agent
                             24 February 2016

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           IBM Rational License Key Server
Publisher:         IBM
Operating System:  AIX
                   HP-UX
                   Linux variants
                   Solaris
                   Windows
Impact/Access:     Access Privileged Data         -- Remote with User Interaction
                   Modify Arbitrary Files         -- Remote/Unauthenticated      
                   Denial of Service              -- Remote/Unauthenticated      
                   Provide Misleading Information -- Remote with User Interaction
Resolution:        Patch/Upgrade
CVE Names:         CVE-2016-0466 CVE-2016-0448 CVE-2015-7575
                   CVE-2015-4911 CVE-2015-4893 CVE-2015-4803

Reference:         ASB-2016.0004
                   ESB-2016.0430
                   ESB-2016.0413
                   ESB-2016.0049
                   ESB-2016.0047
                   ESB-2016.0046

Original Bulletin: 
   http://www-01.ibm.com/support/docview.wss?uid=swg21976926

Revision History:  February 24 2016: Additional CVEs added to the bulletin
                   February 23 2016: Initial Release

- --------------------------BEGIN INCLUDED TEXT--------------------

http://www-01.ibm.com/support/docview.wss?uid=swg21976926
Security Bulletin: Multiple Security Vulnerabilities in IBM Java Runtime
affect IBM RLKS Administration and Reporting Tool Admin and Agent

Security Bulletin

Document information

More support for:

Rational License Key Server

RLKS Administration and Reporting Tool

Software version:

8.1.4, 8.1.4.1, 8.1.4.2, 8.1.4.3, 8.1.4.4, 8.1.4.5, 8.1.4.6, 8.1.4.7,
8.1.4.8, 8.1.4.9

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1976926

Modified date:

2016-02-23

Summary

There are multiple vulnerabilities in IBM Runtime Environment Java Technology
Edition, Versions 6.0.16.0 and 7.0.9.10, that are used by IBM Rational
License Key Server Administration and Reporting Tool Admin and Agent. These
issues were disclosed as part of the IBM Java Runtime updates in January 2016
and includes the vulnerability commonly referred to as SLOTH.

Vulnerability Details

CVEID:

CVE-2016-0466

DESCRIPTION:

An unspecified vulnerability in Oracle Java SE Java SE Embedded and Jrockit
related to the JAXP component could allow a remote attacker to cause a denial
of service resulting in a partial availability impact using unknown attack
vectors.

CVSS Base Score: 5

CVSS Temporal Score: See

https://exchange.xforce.ibmcloud.com/vulnerabilities/109948

for the current score

CVSS Environmental Score*: Undefined

CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)

CVEID:

CVE-2015-7575

DESCRIPTION:

The TLS protocol could allow weaker than expected security caused by a
collision attack when using the MD5 hash function for signing a
ServerKeyExchange message during a TLS handshake. An attacker could exploit
this vulnerability using man-in-the-middle techniques to impersonate a TLS
server and obtain credentials.

CVSS Base Score: 7.1

CVSS Temporal Score: See

https://exchange.xforce.ibmcloud.com/vulnerabilities/109415

for the current score

CVSS Environmental Score*: Undefined

CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N)

CVEID:

CVE-2016-0448

DESCRIPTION:

An unspecified vulnerability in Oracle Java SE and Java SE Embedded related
to the JMX component could allow a remote attacker to obtain sensitive
information resulting in a partial confidentiality impact using unknown
attack vectors.

CVSS Base Score: 4

CVSS Temporal Score: See

https://exchange.xforce.ibmcloud.com/vulnerabilities/109949

for the current score

CVSS Environmental Score*: Undefined

CVSS Vector: (AV:N/AC:L/Au:S/C:P/I:N/A:N)

CVEID:

CVE-2015-4893

DESCRIPTION:

An unspecified vulnerability related to the JAXP component could allow a
remote attacker to cause a denial of service.

CVSS Base Score: 5

CVSS Temporal Score: See

https://exchange.xforce.ibmcloud.com/vulnerabilities/107359

for the current score

CVSS Environmental Score*: Undefined

CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)

CVEID:

CVE-2015-4803

DESCRIPTION:

An unspecified vulnerability related to the JAXP component could allow a
remote attacker to cause a denial of service.

CVSS Base Score: 5

CVSS Temporal Score: See

https://exchange.xforce.ibmcloud.com/vulnerabilities/107358

for the current score

CVSS Environmental Score*: Undefined

CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)

CVEID:

CVE-2015-4911

DESCRIPTION:

An unspecified vulnerability related to the JAXP component could allow a
remote attacker to cause a denial of service.

CVSS Base Score: 5

CVSS Temporal Score: See

https://exchange.xforce.ibmcloud.com/vulnerabilities/107360

for the current score

CVSS Environmental Score*: Undefined

CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)

Affected Products and Versions

These vulnerabilities impact following components and their releases:

RLKS Administration and Reporting Tool version 8.1.4

RLKS Administration and Reporting Tool version 8.1.4.2

RLKS Administration and Reporting Tool version 8.1.4.3

RLKS Administration and Reporting Tool version 8.1.4.4

RLKS Administration and Reporting Tool version 8.1.4.5

RLKS Administration and Reporting Tool version 8.1.4.6

RLKS Administration and Reporting Tool version 8.1.4.7

RLKS Administration and Reporting Tool version 8.1.4.8

RLKS Administration and Reporting Tool version 8.1.4.9

RLKS Administration Agent version 8.1.4

RLKS Administration Agent version 8.1.4.2

RLKS Administration Agent version 8.1.4.3

RLKS Administration Agent version 8.1.4.4

RLKS Administration Agent version 8.1.4.5

RLKS Administration Agent version 8.1.4.6

RLKS Administration Agent version 8.1.4.7

RLKS Administration Agent version 8.1.4.8

RLKS Administration Agent version 8.1.4.9

RLKS LKAD Borrow Tool version 8.1.4

RLKS LKAD Borrow Tool version 8.1.4.8

Remediation/Fixes

Replace the JRE used in IBM RLKS Administration and Reporting Tool and IBM
RLKS Administration Agent.

Steps to replace the JRE in IBM RLKS Administration and Reporting Tool (All
Versions)

1. Go to Fix Central

2. On the Find product tab, enter Rational Common Licensing in the Product 
Selector field and hit enter.

3. Select the Installed Version and hit continue button.

4. Select the platform of the machine where RLKS Administration and Reporting
Tool is installed and hit continue button.

5. On the Identify fixes page, select Browse for fixes and select Show fixes 
that apply to this version and hit continue button.

6. Download the Java 6 runtime iFix for RLKS Administration and Reporting Tool.

Note:

Although the name of the iFix is

RLKS_Administration_And_Reporting_Tool_8149_iFix_3_<Platform>_<Architecture>

, the same ifix is applicable to all previous RLKS Administration and
Reporting Tool versions.

7. Shutdown RLKS Administration and Reporting Tool.

8. Go to the installation location of RLKS Administration and Reporting Tool.

9. Rename <install location>/server/jre folder to

<install location>/server/jre_back

. This step backs up the existing JRE.

10. Extract the downloaded JRE into <install location>/server folder.

Example: <install location>/server/jre

11. Startup RLKS Administration and Reporting Tool.

12. Login to the tool using rcladmin user and verify that you see the
configured license servers under 'Server' tab.

How to fix these vulnerabilities in IBM RLKS Administration Agent (All
Versions)?

1. Go to Fix Central

2. On the Find product tab, enter Rational Common Licensing in the Product 
Selector field and hit enter.

3. Select the Installed Version and hit continue button.

4. Select the platform of the machine where RLKS Administration Agent is
installed and hit continue button.

5. On the Identify fixes page, select Browse for fixes and select Show fixes 
that apply to this version and hit continue button.

6. Download the Java 7 runtime iFix for RLKS Administration Agent.

Note:

Although the name of the iFix is 
RLKS_Administration_And_Reporting_Tool_8149_iFix_3_<Platform>_<Architecture>, 
the same ifix is applicable to all previous RLKS Administration Agent versions.

7. Shutdown RLKS Administration Agent.

8. Go to the installation location of RLKS Administration Agent.

9. Rename <install location>/jre folder to <install location>/jre_back. This 
step backs up the existing JRE.

10. Extract the downloaded JRE into <install location> folder.

Example: <install location>/jre

11. Startup RLKS Administration Agent.

Steps to replace the JRE in IBM RLKS LKAD Borrow Tool (All Versions)

1. Go to Fix Central

2. On the Find product tab, enter Rational Common Licensing in the Product 
Selector field and hit enter.

3. Select the Installed Version and hit continue button.

4. Select Windows as the platform and hit continue button.

5. On the Identify fixes page, select Browse for fixes and select Show fixes 
that apply to this version and hit continue button.

6. Download the Java 6 runtime iFix for RLKS LKAD Borrow Tool.

7. Close RLKS LKAD Borrow Tool.

8. Go to the installation location of LKAD Borrow Tool.

9. Rename <install location>/jre folder to <install location>/jre_back. This 
step backs up the existing JRE.

10. Extract the downloaded JRE into <install location> folder.

Example: <install location>/jre

11. Launch RLKS LKAD Borrow Tool.

Get Notified about Future Security Bulletins

Subscribe to

My Notifications

to be notified of important product support alerts like this.

References

Complete CVSS v2 Guide


On-line Calculator v2


Complete CVSS v3 Guide


On-line Calculator v3

IBM Java SDK Security Bulletin

Related information

IBM Secure Engineering Web Portal

IBM Product Security Incident Response Blog

Acknowledgement

CVE-2015-7575 was reported to IBM by Karthikeyan Bhargavan at INRIA in Paris,
France.

Change History

23 February 2016 : Original 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.

- --------------------------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:

        http://www.auscert.org.au/render.html?cid=1980

===========================================================================
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

iQIVAwUBVs0XiX6ZAP0PgtI9AQJ+zg/9HTmyW0UpfUXE8km+9cMvy9PwyXgBiK+L
1L/cU8vq/HVCw+EBx4zWTjBo5e28DVjYcMI9K3yEGRJyQnL7zgwRq/w6Af1LdiwL
cfVX4B14xrHN2KCrbnT0xw3tLpoBHa41vhVIgY1OQibD/pwQmijM30Gwf1jTz5QT
emsQE26oWEmcseMrJMhUSEftBuE3tkc3SbM1wrR/3jmTUUhhMgLqLB2En4G2D5wF
3v1QaP2v4yej3fOZn+7WnZNPQaYj0R0iVgA2cixwdNiuHJ8a9yV5twM/C7rUGVjT
spUbDaMsvn5bYavGKRgMqS2su370IEqf7SaTky1yDXgf9n+V8WypLX+2X4agR1Kj
K9EcYDma1XdrfO7nQqNiy/QiY6o9leusHpFObxdLPKLZgo3Uch2AwIWLM5VX6OCl
A0wfsjGcIYuwiCvqTkezvJ8zd4wrYW2RggKfe4RrIuZ/qJGjuWo/2S4t3zXEy6Cw
eT2upXPfsms6cDts61XulRt7LigRkCGV9yIyueHubOlQuZq5dH7y1CE+7JvYtqe4
qnyWO5gaeuPLYMA2DTFN2T9E5ed+PSBxXiCu/iaw2WuVWOvGL17Y7pWI2LElhnbE
lMO/I91j3reM+MmY1rH8yJCldiSxn1aIkXrVWNYE4DifF6lIACj1dNc80h6WyUFA
hHA7lHe2Sjk=
=dIcw
-----END PGP SIGNATURE-----