IBM DB2 contains a security vulnerability which could allow a remote, authenticated user to exploit a vulnerability in DB2's XML library to cause a disruption of service.
CVE ID: CVE-2014-8901
IBM DB2 contains a disruption of service vulnerability. A remote, authenticated user can issue a specially crafted XML query to cause DB2 to increase CPU usage and create serious performance degradation to the system.
CVSS Base Score: 4.0
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/99110 for the current score
CVSS Environmental Score*: Undefined
CVSS String: (AV:N/AC:L/Au:S/C:N/I:N/A:P)
Affected Products and Versions
All fix pack levels of IBM DB2 V9.5, V9.7, V10.1 and V10.5 editions listed below and running on AIX, Linux, HP, Solaris or Windows are affected.
IBM 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 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 DB2 Connect products mentioned are affected only if a local database has been created.
IBM DB2 pureScale™ Feature for Enterprise Server Edition, V9.8, running on AIX or Linux is affected.
The recommended solution is to apply the appropriate fix for this vulnerability.
The fix for DB2 and DB2 Connect V9.7 is in V9.7 FP11, V10.1 is in V10.1 FP5 and V10.5 is in V10.5 FP5 which are available for download from Fix Central.
Customers running any vulnerable fixpack level of an affected Program, V9.5 or V9.8 can contact support to obtain a special build containing an interim fix for this issue. These special builds are available based on the most recent fixpack level for each impacted release: DB2 V9.5 FP10 or DB2 V9.8 FP5. They can be applied to any affected fixpack level of the appropriate release to remediate this vulnerability. Additionally fixes based on DB2 V9.5 FP9, V9.7 FP10, DB2 V10.1 FP4 or V10.5 FP4 will be made available on request.
Refer to the folowing chart to determine how to proceed to obtain a needed fixpack or special build.
|Release||Fixed in fix pack||APAR||Download URL|
|V9.5||TBD||IT05936||Please contact technical support.|
|V9.8||TBD||IT05938||Please contact technical support.|
Contact Technical Support:
Note: IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.
Workarounds and Mitigations
Get Notified about Future Security Bulletins
The vulnerability was reported to IBM by Danny Tsechansky of McAfee Database Security Research.
December 15, 2014: Original Version Published
June 19, 2015: Updated with V10.1 FP5 fix info.
October 2, 2015: Updated with V9.7 FP11 fix info.
*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