A vulnerability in IBM DB2 for Linux, Unix and Windows could allow a local user to gain elevated privilege.
DESCRIPTION: DB2 for Linux, Unix and Windows is vulnerable to a privilege escalation due to loading libraries from insecure locations. A local user could place a malicious library in a location that a SETGID or SETUID binary would execute and gain root level access.
CVSS Base Score: 8.4
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116653 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
The following IBM DB2 and DB2 Connect editions running on AIX, Linux and HP are vulnerable.
BM® DB2® Express Edition
IBM® DB2® Workgroup Server Edition
IBM® DB2® Enterprise Server Edition
IBM® DB2® Advanced Enterprise Server Edition
IBM® DB2® Advanced Workgroup Server Edition
IBM® DB2® Direct Advanced Edition
IBM® DB2® Direct Standard Edition
IBM® DB2® Connect™ Application Server Edition
IBM® DB2® Connect™ Enterprise Edition
IBM® DB2® Connect™ Unlimited Edition for System i®
IBM® DB2® Connect™ Unlimited Edition for System z®
The IBM data server client and driver types are as follows:
IBM Data Server Driver Package
IBM Data Server Driver for ODBC and CLI
IBM Data Server Runtime Client
IBM Data Server Client
The following table details which DB2 release, fixpacks and platforms are affected:
|V10.5||FP7||All except Windows, Solaris SPARC and Solaris x86|
|V11.1.1||GA||Linux Power™ little endian and Linux System z®|
The recommended solution is to apply the appropriate fix for this vulnerability.
The fix for DB2 and DB2 Connect is in V10.1 FP6, V10.5 FP8 and V11.1.1 FP1, available for download from Fix Central.
Customers running any vulnerable fixpack level of an affected Program, V9.7 can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent fixpack level for each impacted release: DB2 V9.7 FP11. They can be applied to any affected fixpack level of the appropriate release to remediate this vulnerability.
Refer to the following chart to determine how to proceed to obtain a needed fixpack or special build.
|Release||Fixed in fix pack||APAR||Download URL|
|V9.7||TBD||IT17010||Special Build for V9.7 FP11: |
Linux 64-bit, POWER™
Workarounds and Mitigations
The following remediation instructions will remove the vulnerability without side-effects. The user executing the commands must be root and the instructions must be repeated for each DB2 instance and in the DB2 install directory.
The following example will use /home/db2inst1/sqllib as the DB2 instance install directory. You should replace the sample directory with your DB2 instance install directory. Repeat the procedure with the DB2 install directory which is under /opt/ibm/db2/<db2_release_name> or /opt/IBM/db2/<db2_release_name>, depending on the platform.
The following will fix the install component that exists at the DB2 client and server.
bin/db2chglibpath -s '\.:' -r '' adm/db2iclean
Get Notified about Future Security Bulletins
September 15, 2016: Original version published.
September 26, 2016: Corrected the list of DB2 editions.
December 15, 2016: Updated bulletin with V11.1.1 FP1 Fix Central URL.
February 28, 2017: Updated bulletin with V10.1 FP6 Fix Central URL.
*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.
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.
16 June 2018