home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT04730 Status: Closed

SECURITY: DB2 may terminate abnormally when issuing an ALTER TAB LE
statement with AUTO_REVAL set to IMMEDIATE (CVE-2014-6159).

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Under rare circumstances, an ALTER TABLE statement may cause the 
DB2 server to terminate abnormally if AUTO_REVAL is set to 
IMMEDIATE.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 systems on all Linux, Unix and Windows platforms at  * 
* service levels Version 10.5 GA  through to Version 10.5 Fix  * 
* Pack 4.                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 5 or see "Local Fix"    * 
* portion for other suggestions.                               * 
* See security bulletin for more details:                      * 
* http://www-01.ibm.com/support/docview.wss?uid=swg21688051    * 
****************************************************************
Local Fix:
Set database configuration parameter AUTO_REVAL to a value other 
than IMMEDIATE.
Solution
The complete fix for this problem first appears in DB2 Version 
10.5 Fix Pack 5 and all the subsequent Fix Packs.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.10.2014
11.12.2014
11.12.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList