Vulnerability in IBM DB2 could allow an authenticated user, without proper authorization, to read XML files.
CVE ID: CVE-2012-2196
The IBM DB2 products listed below contain a security vulnerability that could
allow an authenticated user, without proper authority, to read XML files. The XML files are any files that end with the xml extension. The process running the vulnerable code is executing with the privilege of the DB2 fenced ID. Hence, it can read any XML files which the DB2 fenced ID has read privilege. On the Windows platform, the DB2 fenced ID has administrator privilege.
The routines containing the vulnerability are GET_WRAP_CFG_C and GET_WRAP_CFG_C2, and PUBLIC is granted EXECUTE privilege on these routines. These routines are used only when using DB2 Control Center to assist with tasks on the DB2 database instances. If you are not using the Control Center then the vulnerability may be mitigated by revoking EXECUTE privilege on these routines from PUBLIC.
CVSS Base Score: 4
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/76276 for the current score
CVSS Environmental Score*: Undefined
CVSS String: (AV:N/AC:L/Au:S/C:P/I:N/A:N)
The following IBM DB2 V9.1, V9.5, V9.7 and V10.1 editions running on AIX, Linux, HP, Solaris and Windows:
IBM® DB2® 10.1 Express Edition
IBM® DB2® 10.1 Workgroup Server Edition
IBM® DB2® 10.1 Enterprise Server Edition
IBM® DB2® 10.1 Advanced Enterprise Server Edition
IBM® DB2® Connect™ 10.1 Application Server Edition
IBM® DB2® Connect™ 10.1 Enterprise Edition
IBM® DB2® Connect™ 10.1 Unlimited Edition for System i®
IBM® DB2® Connect™ 10.1 Unlimited Edition for System z®
IBM® DB2® 9.7 Express Edition
IBM® DB2® 9.7 Workgroup Server Edition
IBM® DB2® 9.7 Enterprise Server Edition
IBM® DB2® 9.7 Advanced Enterprise Server Edition
IBM® DB2® Connect™ 9.7 Application Server Edition
IBM® DB2® Connect™ 9.7 Enterprise Edition
IBM® DB2® Connect™ 9.7 Unlimited Edition for System i®
IBM® DB2® Connect™ 9.7 Unlimited Edition for System z®
IBM® DB2® 9.5 Express Edition
IBM® DB2® 9.5 Workgroup Server Edition
IBM® DB2® 9.5 Enterprise Server Edition
IBM® DB2® 9.5 Advanced Enterprise Server Edition
IBM® DB2® Connect™ 9.5 Application Server Edition
IBM® DB2® Connect™ 9.5 Enterprise Edition
IBM® DB2® Connect™ 9.5 Unlimited Edition for System i®
IBM® DB2® Connect™ 9.5 Unlimited Edition for System z®
IBM® DB2® 9.1 Express Edition
IBM® DB2® 9.1 Workgroup Server Edition
IBM® DB2® 9.1 Enterprise Server Edition
IBM® DB2® 9.1 Advanced Enterprise Server Edition
IBM® DB2® Connect™ 9.1 Application Server Edition
IBM® DB2® Connect™ 9.1 Enterprise Edition
IBM® DB2® Connect™ 9.1 Unlimited Edition for System i®
IBM® DB2® Connect™ 9.1 Unlimited Edition for System z®
NOTE: The DB2 Connect products mentioned are affected only if a local database has been created.
The following IBM V9.8 editions running on AIX and Linux:
IBM® DB2® pureScale™ Feature for Enterprise Server Edition
The recommended solution is to apply the appropriate fix for this vulnerability. Mitigation is also available.
The fix for this vulnerability is available for download for DB2 release V9.1 FP12, V9.5, FP10, V9.7 FP7 and V10.1 FP1. For DB2 V9.8 the fix is planned to be made available in future fix packs.
In general, DB2 fix packs can be downloaded from the following site: http://www.ibm.com/support/docview.wss?uid=swg27007053. You may download the specific fix pack you need from the following:
|V9.8||IC84750||Not available. Please contact technical support.|
A special build with the interim fix will be made available for V9.8 FP5. Please contact your service representative to obtain the special build and reference the APAR number for the release you want.
Contact Technical Support:
In the United States and Canada dial 1-800-IBM-SERV
View the support contacts for other countries outside of the United States.
Electronically open a Service Request with DB2 Technical Support.
None known; apply fixes
To exploit the vulnerability, the user would need to be able to connect to the database and call the routine GET_WRAP_CFG_C or GET_WRAP_CFG_C2. Revoking EXECUTE privilege from PUBLIC on these routines would allow you to control who can call the routines. Use the following SQL statement to revoke the privilege:
REVOKE EXECUTE ON SYSPROC.GET_WRAP_CFG_C FROM PUBLIC
REVOKE EXECUTE ON SYSPROC.GET_WRAP_CFG_C2 FROM PUBLIC
To obtain more information on the REVOKE routine privileges statement, see the following for DB2 V10.1. The statement syntax is the same for other DB2 releases.
This vulnerability was reported to IBM by Martin Rakhmanov of Application Security Inc.
August 8, 2012: Document created.
August 21, 2012 - V9.5 FP10 has shipped. Updated document to include V9.5 FP10 download URL.
September 17, 2012 - DB2 V10.1 FP1 has shipped. Updated document to include V10.1 FP1 download URL.
November 6, 2012 - V9.7 FP7 has shipped. Updated document to include V9. FP7 download 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 Flash.
Note: 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
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.
16 June 2018