When a table is renamed and a new table is created with the old name, users who had access on the old table may be able to access the new table.
A user may incorrectly acquire privileges on a table if the table is created with the same name as a previously renamed table. During a RENAME TABLE, a user maintains privileges on the renamed table. However, if a new table is then created with the old name, the user may also incorrectly maintain their privileges on this new table. The problem is caused by the rename operation not updating the user authorization cache. The error will be cleared up when the database is deactivated or when the DB2 instance is restarted.
User A is granted select privilege to table ABC.T1
An authorized user renames table ABC.T1 to ABC.T2
An authorized user creates a new table called ABC.T1
User A can correctly select from ABC.T2 (the new name for the renamed table) but will incorrectly gain the ability to select from ABC.T1 (new table)
DESCRIPTION: IBM DB2 for Linux, UNIX and Windows (includes DB2 Connect Server) could allow an authenticated attacker with specialized access to tables that they should not be permitted to view.
CVSS Base Score: 3.1
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/122291 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N)
Affected Products and Versions
All fix pack levels of IBM DB2 V10.1, V10.5 and V11.1 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® 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 DB2 Connect products mentioned are affected only if a local database has been created.
The recommended solution is to apply the appropriate fix for this vulnerability.
The fix for DB2 and DB2 Connect release is in V10.1 FP6 is available for download from Fix Central.
Customers running any vulnerable fixpack level of an affected Program, V10.5 and V11.1 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 V10.5 FP8 and DB2 V11.1.1 FP1. They can be applied to any affected fixpack level of the appropriate release to remediate this vulnerability.
|Release||Fixed in fix pack||APAR||Download URL|
Workarounds and Mitigations
Recycling the database:
- Create a new table with the old table name.
- For each affected grantee:
- Grant the privilege(s) held by the grantee on the old table.
- Revoke the granted privilege(s) from step a.
- Drop the table created on step 1 (if not needed anymore).
Revoke all the privileges from other grantees prior to the RENAME TABLE and re-grant the privileges to the grantees on the newly named table.
Get Notified about Future Security Bulletins
February 28, 2017: Original version published.
March 2, 2017: Clarified wordings in Vulnerability Details
April 27, 2017: Updated V11.1.1 iFix001 download URL.
October 11, 2017: Updated V10.5 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 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