DB2 - Problem description
Problem IT06350 | Status: Closed |
SECURITY: TLS padding vulnerability affects IBM© DB2© LUW (CVE-2014-8730) | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
The TLS padding vulnerability could allow a remote attacker to obtain sensitive information, caused by the failure to check the contents of the padding bytes when using CBC cipher suites of some TLS implementations. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) like attack to decrypt sensitive information and calculate the plaintext of secure connections. Customers have Secure Sockets Layer (SSL) support enabled in their DB2 database system are affected. SSL support is not enabled in DB2 by default. | |
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. * * Refer to security bulletin for details: * * http://www-01.ibm.com/support/docview.wss?uid=swg21693011 * **************************************************************** | |
Local Fix: | |
This problem can be mitigated by setting the operating system environment variable GSK_STRICTCHECK_CBCPADBYTES=GSK_TRUE. Please refer to security bulletin for detail mitigation instruction : http://www-01.ibm.com/support/docview.wss?uid=swg21692618 | |
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 : | 07.01.2015 14.07.2015 14.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 |