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 IT05647 Status: Closed

SECURITY: ALTER TABLE on an identity column may cause DB2 to terminate
(CVE-2014-6209).

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 contains a vulnerability in which an ALTER TABLE statement 
may cause the DB2 server to terminate abnormally. This would 
result in a DB2 server crash which would have to be restarted.
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 4.                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5 or see "Local Fix"    * 
* portion for other suggestions.                               * 
****************************************************************
Local Fix:
See security bulletin for details: 
http://www-01.ibm.com/support/docview.wss?uid=swg21690787.
Solution
The complete fix for this problem first appears in DB2 Version 
10.1 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       :
18.11.2014
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList