ESB-2018.3712 - [Win][Linux][HP-UX][Solaris][AIX] IBM DB2 Recovery Expert: Multiple vulnerabilities 2018-11-29

Printable version
PGP/GPG verifiable version

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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

                               ESB-2018.3712
       Vulnerability in IBM Java Runtime affect DB2 Recovery Expert
                        for Linux, Unix and Windows
                             29 November 2018

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

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

Product:           IBM DB2 Recovery Expert
Publisher:         IBM
Operating System:  AIX
                   HP-UX
                   Linux variants
                   Solaris
                   Windows
Impact/Access:     Access Privileged Data -- Remote/Unauthenticated
                   Modify Arbitrary Files -- Remote/Unauthenticated
                   Delete Arbitrary Files -- Remote/Unauthenticated
                   Denial of Service      -- Remote/Unauthenticated
Resolution:        Patch/Upgrade
CVE Names:         CVE-2018-3180  

Reference:         ASB-2018.0256
                   ESB-2018.3705
                   ESB-2018.3623
                   ESB-2018.3621
                   ESB-2018.3599

Original Bulletin: 
   https://www.ibm.com/support/docview.wss?uid=ibm10742763

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

Security Bulletin: Vulnerability in IBM Java Runtime affect DB2 Recovery Expert
for Linux, Unix and Windows

Security Bulletin

Document information

Software version: 5.1.0
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows
Reference #: 0742763
Modified date: 28 November 2018

Summary

There is vulnerability in IBM(R) Runtime Environment Java(TM) Version Java 1.8.0 SR5
FP16 and earlier used by DB2 Recovery Expert for Linux, Unix and Windows. These
issues were disclosed as part of the IBM Java SDK updates in Oct. 2018.

Vulnerability Details

CVEID: CVE-2018-3180

 

DESCRIPTION: Vulnerability in the Java SE, Java SE Embedded, JRockit component
of Oracle Java SE (subcomponent: JSSE). Supported versions that are affected
are Java SE: 6u201, 7u191, 8u182 and 11; Java SE Embedded: 8u181; JRockit:
R28.3.19. Difficult to exploit vulnerability allows unauthenticated attacker
with network access via SSL/TLS to compromise Java SE, Java SE Embedded,
JRockit. Successful attacks of this vulnerability can result in unauthorized
update, insert or delete access to some of Java SE, Java SE Embedded, JRockit
accessible data as well as unauthorized read access to a subset of Java SE,
Java SE Embedded, JRockit accessible data and unauthorized ability to cause a
partial denial of service (partial DOS) of Java SE, Java SE Embedded, JRockit.
Note: This vulnerability applies to Java deployments, typically in clients
running sandboxed Java Web Start applications or sandboxed Java applets (in
Java SE 8), that load and run untrusted code (e.g. code that comes from the
internet) and rely on the Java sandbox for security. This vulnerability can
also be exploited by using APIs in the specified Component, e.g. through a web
service which supplies data to the APIs.
CVSS Base Score: 5.6
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/
151497 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:L)

 

Affected Products and Versions

DB2 Recovery Expert for LUW  5.1
DB2 Recovery Expert for LUW  5.1 Interim Fix 1 (IF1)
DB2 Recovery Expert for LUW  5.1.0.1 (also called 5.1 Fix Pack 1)
DB2 Recovery Expert for LUW  5.1.0.1 IF1
DB2 Recovery Expert for LUW  5.1.0.1 IF2
DB2 Recovery Expert for LUW  5.1.0.2 (also called 5.1 Fix Pack 2)
DB2 Recovery Expert for LUW  5.1.0.2 IF1
DB2 Recovery Expert for LUW  5.1.0.3 (also called 5.1 Fix Pack 3)


Remediation/Fixes

+----------+---------+----------------------------------------------------+
|Product   |VRMF     |Remediation/First Fix                               |
+----------+---------+----------------------------------------------------+
|DB2       |         |                                                    |
|Recovery  |will be  |https://www.ibm.com/support/fixcentral/swg/         |
|Expert for|fixed in |selectFixes-parent=ibm%7EInformation%20Management&  |
|Linux,    |future   |product=ibm/Information+Management/                 |
|Unix and  |V5.1.0.3 |DB2+Recovery+Expert+for+Linux+UNIX+and+Windows&     |
|Windows   |IF 1     |release=All&platform=All&function=all               |
+----------+---------+----------------------------------------------------+

 

Workarounds and Mitigations

There are no workarounds except to replace to the latest JRE.
To solve the problem without updating the entire Recovery Expert product, the
user can replace the existing JRE that is installed into the product
installation tree in the "jre" directory with a newer JRE that includes the
security fixes.

Instructions to replace the IBM JRE for DB2 Recovery Expert for Linux, UNIX and
Windows

1. Identify the version and platform of your DB2 Recovery Expert installation.
2. See the table below to find the IBM JRE download link that matches your
product version and platform. If you cannot find a JRE download link for your
product version and platform, contact IBM Technical Support and refer to this
tech-note
3. Download the zip file (for example: ibm-java-jre-x.x-x.x-linux-x86_64.tgz)
and extract it to a folder on a local file system (for example: /tmp/
ibm-jre-x.x-x.x).
4. Stop the DB2 Recovery Expert server using the stop.sh command (for example:
/opt/ibm/RE/stop.sh).
5. Back-up and then delete the contents of the "jre" folder from your product
installation directory (for example: /opt/ibm/RE/jre).
6. Copy the contents of the "jre" folder from the latest IBM JRE that you
downloaded in Step 3 (for example: /tmp/ibm-jre-x.x-x.x/jre/) to the "jre"
folder in your product installation directory (for example: /opt/ibm/RE/jre/).*
7. Ensure that the file permissions for the new JRE files and folders match the
file permissions for the original JRE files and folders. If necessary, set 775
recursively.
8. Restart the DB2 Recovery Expert server using the start.sh command (for
example: /opt/ibm/RE/start.sh).

* NOTE: You must repeat from Step 6 again any time you install an APAR or
upgrade to an affected version of DB2 Recovery Expert.


Reference

Complete CVSS v2 Guide
On-line Calculator v2

Complete CVSS v3 Guide
On-line Calculator v3

Related Information

IBM Secure Engineering Web Portal
IBM Product Security Incident Response Blog

Acknowledgement

None

Change History

28 Nov 2018

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

        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

iQIVAwUBW/9wwmaOgq3Tt24GAQhsiRAAwLjIcGECIWhQT65dO/9gz0rrr7v9cfSR
OLG+C5RvSTPTV4C6P23qLGyddF1RspxKeQodGxoO2GykwgV/w3EY72Hc8H/ODf2b
PACeq8ewQBk7T+BTnPtLi183v6eBudDOi9AguEB97FUawopPIsFQcCD0Qv1eVyce
7GKKZt01y3aDP+camwoulZGQuug/tie+PN/QBS3rueAF7ctAX2rBGOEyaqf4NQvn
UZdGB8DuqPGol4A/x7FelTASZCPN1JH+7DXTZDUIvkJaS/4dbVYLki67sU68uUKl
nX/XJnCfe1tyTXQaaYKgs/Mq/n3OAZ/VUELkYDOmsm/6L4Rqpe4539Xs3yeb0NzE
T8qTddy3+zjuc+K6wdJm7AtXTHIt3D7KHSYoGNUa23NlNnhLkg9cSgDe71jFF3WP
j5w+rUubcmr2TcR6CoAWoUR+UcbnNNZUJ+DpZNsmCLMqrqF+iBHis8E2mc6V2Tmu
bpLtpxHF+39viIXmBJ49KUG4uxnH75mW+VUDeKtmPZidHNrvEiIcDxCAwko+YAjs
83Xzti0VFppOGnSfpXSVFrMdJeuRGMi8gKxc67daWqcucTAaDrStqWwi4xnUU+gp
zqUNxKGMu70UH8blW2bC1Jz+0qwSZdQ/W1qEksYqpJzU1f8EgtBe3/maePnczIyZ
1pW7DxM4QY4=
=J0U2
-----END PGP SIGNATURE-----

« Back to bulletins