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

CLIENT LOAD CAN FAIL DUE TO MEMORY OVERWRITE BECAUSE OF INCORRECT INPUT
PARSING

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
A client side load will send the data and some conrol 
information across to the server using the DRDA communication 
protocol. 
In very rare circumstances, it is possible that a split DRDA 
message is wrongly interpreted by the DB2 server. 
This then leads to the load code wrongly interpreting a length 
which can trigger a large memory overwrite. 
 
As the overwrite can be large in size, the EDU detecting the 
problem is likely not the one causing the problem, so a stack 
will not directly point to this problem. 
The key factor leading to this problem is that a ( large ) 
client side load was happening at the time of the problem.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the DB2 Server to V10.1 Fix Pack 5 or higher.        * 
****************************************************************
Local Fix:
Solution
This problem was first fixed in v10.1 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2014
27.07.2015
27.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