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

SECURITY: DB2 CLP WILL TRAP IF IT IS PASSED A ROUTINE NAME GREATER THEN THE
ALLOWED MAXIMUM LENGTH (CVE-2017-1297).

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
DB2 Command Line Processor (CLP) background process (db2bp) will 
trap if CLP is passed a CALL statement containing a routine name 
greater then 386 characters. 
 
See security bulletin for details: 
http://www-01.ibm.com/support/docview.wss?uid=swg22004878
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 systems on all Linux, Unix and Windows platforms at  * 
* service levels Version 11.1 GA  through to Version 11.1 Fix  * 
* Pack 1.                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 11.1.2 Fix Pack 2 or see "Local Fix"  * 
* portion for other suggestions.                               * 
****************************************************************
Local Fix:
Perform length check on routine names in CLP CALL statements to 
disallow name length greater then 386 characters.
available fix packs:
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
The complete fix for this problem first appears in DB2 Version 
11.1.2 Fix Pack 2 and all the subsequent Fix Packs.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.05.2017
21.06.2017
21.06.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)