DB2 - Problem description
Problem IC72118 | Status: Closed |
Users able to update statistics for tables without appropriate privileges | |
product: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problem description: | |
Users are able to incorrectly update statistics columns in SYSSTAT.TABLES for tables upon which they do not have appropriate privileges. Thus, a malicious user may be able to introduce query performance degradations by modifying table statistics via this view. Normally, in order to update the statistics for a table via this view, you must have CONTROL or explicit DATAACCESS privilege on the table. This APAR fix addresses this problem. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users running on Linux, Unix and Windows servers on DB2 * * v9.1 Fix Pack 9 and earlier are affected. * **************************************************************** * PROBLEM DESCRIPTION: * * The view text of SYSSTAT.TABLES is suppose to limit the rows * * returned according to the user privileges, but the view is * * returning more rows than it should be. Thus, allowing users * * to modify the statistics for tables they don't have the * * necessary privileges on. * **************************************************************** * RECOMMENDATION: * * Refer to Local Fix or update to DB2 v9.1 Fix Pack 10. * **************************************************************** | |
Local Fix: | |
Revoke UPDATE privilege from PUBLIC on the SYSSTAT.TABLES view until this APAR is applied. Namely, run: revoke update on sysstat.tables from public You may continue updating statistics with appropriate privileges via the SYSCAT.TABLES view if needed, which is not affected by this problem. | |
available fix packs: | |
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows | |
Solution | |
The problem is first fixed in DB2 v9.1 Fix Pack 10. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.10.2010 05.07.2011 05.07.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.1.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.10 |