Security Bulletin
Summary
DB2 Recovery Expert for Linux, UNIX and Windows has addressed the following vulnerabilities:IBM SDK, Java Technology Edition Quarterly CPU - Jan 2020 - Includes Oracle Jan 2020 CPU minus CVE-2020-2585, CVE-2020-2654, and CVE-2020-2590. These issues were disclosed as part of the IBM Java SDK updates in Jan 2020.
Vulnerability Details
CVEID: CVE-2020-2604
DESCRIPTION: An unspecified vulnerability in Java SE could allow an unauthenticated attacker to take control of the system.
CVSS Base score: 8.1
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/174551 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)
CVEID: CVE-2020-2593
DESCRIPTION: An unspecified vulnerability in Java SE related to the Java SE 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/174541 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)
CVEID: CVE-2020-2659
DESCRIPTION: An unspecified vulnerability in Java SE related to the Java SE Networking component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.
CVSS Base score: 3.7
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/174606 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L)
CVEID: CVE-2020-2583
DESCRIPTION: An unspecified vulnerability in Java SE related to the Java SE Serialization component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.
CVSS Base score: 3.7
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/174531 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L)
CVEID: CVE-2019-4732
DESCRIPTION: IBM SDK, Java Technology Edition Version 7.0.0.0 through 7.0.10.55, 7.1.0.0 through 7.1.4.55, and 8.0.0.0 through 8.0.6.0 could allow a local authenticated attacker to execute arbitrary code on the system, caused by DLL search order hijacking vulnerability in Microsoft Windows client. By placing a specially-crafted file in a compromised folder, an attacker could exploit this vulnerability to execute arbitrary code on the system. IBM X-Force ID: 172618.
CVSS Base score: 7.2
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/172618 for the current score.
CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H)
Affected Products and Versions
| Affected Product(s) | Version(s) |
| DB2 Recovery Expert for LUW | 5.5 IF 2 |
Remediation/Fixes
| Product VRMF | Remediation | First Fix |
| DB2 Recovery Expert for Linux, Unix and Windows | Had been fixed in V5.5 IF 2 | https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EInformation%20Management&product=ibm/Information+Management/DB2+Recovery+Expert+for+Linux+UNIX+and+Windows&release=5.5&platform=AIX&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.
Get Notified about Future Security Bulletins
References
Change History
27 Apr 2020: Initial Publication
*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
Review the IBM security bulletin disclaimer and definitions regarding your responsibilities for assessing potential impact of security vulnerabilities to your environment.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
27 April 2020
Initial Publish date:
27 April 2020
UID
ibm16201670