Vulnerability in IBM DB2 XML Feature could allow a remote attacker to view XML files owned by the DB2 instance owner.
CVE ID: CVE-2012-0713
The IBM DB2 products listed below contain a security vulnerability in the DB2 XML Feature which could allow a malicious user to remotely exploit and view XML files owned by the DB2 instance owner. To exploit the vulnerability, the user would need to have valid security credentials, CONNECT privilege to the database and be able to execute a specially crafted SQL statement.
CVSS Base Score: 4
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/73520 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 editions running on AIX, Linux, HP, Solaris and Windows:
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®
The following IBM V9.8 editions running on AIX and Linux:
IBM® DB2® pureScale™ Feature for Enterprise Server Edition
Note: The DB2 Connect products mentioned are affected only if a local database has been created.
Note: The vulnerability does not exist in DB2 V9.1.
There is no workaround but there is mitigation for this vulnerability. Fixes are available as well.
To exploit the vulnerability, the user would need to be able to connect to the database and execute an SQL statement. The exposure can be reduced by revoking CONNECT privilege from PUBLIC. Use the following command to revoke CONNECT privilege from PUBLIC:
REVOKE CONNECT ON DATABASE FROM PUBLIC
To obtain more information on the REVOKE database authority command, see the following:
The fix for this vulnerability is available for download for DB2 release V9.7 Fix Pack 6 and V9.8 Fix Pack 5.
For V9.5, the fix is planned to be made available in a future fix pack.
For V9.1, the vulnerability is not applicable.
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:
A special build with the interim fix will be made available for DB2 V9.5 FP9. Please contact your service representative to obtain the special build and reference the APAR number for the release you want:
Contact Technical Support:
· Complete CVSS v2 Guide
· On-line Calculator V2
· X-Force Vulnerability Database
April 26, 2012: Document created.
August 21, 2012 - V9.5 FP10 has shipped. Updated document to include V9.5 FP10 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