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

SECURITY: DB2 INSTALL USES WEAK PASSWORD ENCRYPTION (CVE-2017-1571)

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
During the DB2 instance creation at silent install time, if the 
user 
invokes the option to have DB2 to create Unix accounts, the 
accounts are created with a saved hashed password that uses the 
DES encryption method.  The accounts that DB2 install can create 
on behalf the user are: DB2 instance, DB2 Administrator Server 
(DAS) and Fenced ID. See Security Bulletin for details: 
http://www-01.ibm.com/support/docview.wss?uid=swg22012948
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 2.                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 11.1.3.3 Fix Pack 3.                  * 
****************************************************************
Local Fix:
The initial password hash uses a weak encryption which can be 
mitigated by changing the password after account creation.
available fix packs:
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.3.3 Fix Pack 3 and all the subsequent Fix Packs.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.09.2017
13.03.2018
13.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)