DB2 - Problem description
Problem IT15485 | Status: Closed |
SECURITY: TABLE PRIVILEGE CHECKING MAY RETURN OUTDATED RESULTS AFTER A TABLE IS RENAMED (CVE-2017-1150) | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All DB2 systems on all Linux, Unix and Windows platforms at * * service levels Version 10.1 GA through to Version 10.1 Fix * * Pack 5. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 6 or see "Local Fix" * * portion for other suggestions. * **************************************************************** | |
Local Fix: | |
See security bulletin for details: http://www-01.ibm.com/support/docview.wss?uid=swg21999515 | |
available fix packs: | |
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows | |
Solution | |
The complete fix for this problem first appears in DB2 Version 10.1 Fix Pack 6 and all the subsequent Fix Packs. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.05.2016 27.04.2017 27.04.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |