Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2014.2441
Security Bulletin: TLS padding vulnerability affects IBM DB2
LUW (CVE-2014-8730)
18 December 2014
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: IBM DB2
Publisher: IBM
Operating System: AIX
HP-UX
Linux variants
Solaris
Windows
Impact/Access: Access Privileged Data -- Remote with User Interaction
Reduced Security -- Remote with User Interaction
Resolution: Patch/Upgrade
CVE Names: CVE-2014-8730
Reference: ESB-2014.2440
ESB-2014.2421
ESB-2014.2407
ESB-2014.2404
ESB-2014.2375
ESB-2014.2325
Original Bulletin:
http://www-01.ibm.com/support/docview.wss?uid=swg21692618
- --------------------------BEGIN INCLUDED TEXT--------------------
Security Bulletin: TLS padding vulnerability affects IBM DB2 LUW
(CVE-2014-8730)
Security Bulletin
Document information
More support for:
DB2 for Linux, UNIX and Windows
Software version:
9.5, 9.7, 9.8, 10.1, 10.5
Operating system(s):
AIX, HP-UX, Linux, Solaris, Windows
Software edition:
Advanced Enterprise Server, Advanced Workgroup Server, Enterprise Server,
Express, Express-C, Personal, Workgroup Server
Reference #:
1692618
Modified date:
2014-12-16
Summary
Transport Layer Security (TLS) padding vulnerability via a POODLE (Padding
Oracle On Downgraded Legacy Encryption) like attack affects IBM DB2 LUW.
Vulnerability Details
CVE-ID: CVE-2014-8730
DESCRIPTION:
Product 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.
CVSS Base Score: 4.3
CVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/99216 for the
current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)
Affected Products and Versions
Customers have Secure Sockets Layer (SSL) support enabled in their DB2
database system are affected. SSL support is not enabled in DB2 by default.
All fix pack levels for IBM DB2 V9.5, V9.7, V10.1 and V10.5 editions listed
below and running on AIX, Linux, HP, Solaris or Windows are affected :
IBM DB2 Express Edition
IBM DB2 Workgroup Server Edition
IBM DB2 Enterprise Server Edition
IBM DB2 Advanced Enterprise Server Edition
IBM DB2 Advanced Workgroup Server Edition
IBM DB2 Connect Application Server Edition
IBM DB2 Connect Enterprise Edition
IBM DB2 Connect Unlimited Edition for System i
IBM DB2 Connect Unlimited Edition for System z
The DB2 Connect products mentioned are affected only if a local database has
been created.
IBM DB2 pureScale Feature for Enterprise Server Edition, V9.8, running on AIX
or Linux is affected.
Remediation/Fixes
None
Workarounds and Mitigations
This problem can be mitigated by setting the operating system environment
variable GSK_STRICTCHECK_CBCPADBYTES.
Customers in the fix pack level of V9.7 FP9, V10.1 FP3a, V10.5 GA or higher
should follow the instruction below to mitigate the problem.
Customer with V9.5 should contact DB2 support to obtain V9.5 FP10a and follow
the instruction below to mitigate the problem.
Customer in fix pack level of V9.7 FP8 or lower, all fix pack level of V9.8 or
V10.1 FP3 or lower should upgrade to the latest fix pack. Then follow the
instruction below to mitigate the problem.
Mitigation instructions:
Customer should set the environment variable GSK_STRICTCHECK_CBCPADBYTES on
each DB2 server instance as follow:
1) As the DB2 instance owner, add the following line to the userprofile file
that is located under the sqllib directory:
export GSK_STRICTCHECK_CBCPADBYTES=GSK_TRUE
2) As a user with DB2 SYSADM privilege, run the following commands:
export GSK_STRICTCHECK_CBCPADBYTES=GSK_TRUE
db2set DB2ENVLIST=GSK_STRICTCHECK_CBCPADBYTES
db2stop
db2start
The commands above assume that DB2ENVLIST registry variable is not set. If it
is set, the environment variable names need to be delimited with a space. For
example, if DB2ENVLIST is already set to SOME_ENV, it needs to be set as
follows:
db2set DB2ENVLIST="SOME_ENV GSK_STRICTCHECK_CBCPADBYTES"
Get Notified about Future Security Bulletins
Subscribe to My Notifications to be notified of important product support
alerts like this.
References
Complete CVSS Guide
On-line Calculator V2
Related information
IBM Secure Engineering Web Portal
IBM Product Security Incident Response Blog
Acknowledgement
None
Change History
December 16, 2014: Original Version Published
*The CVSS Environment Score is customer environment specific and will
ultimately impact the Overall CVSS Score. Customers can evaluate the impact of
this vulnerability in their environments by accessing the links in the
Reference section of this Security Bulletin.
Disclaimer
According to the Forum of Incident Response and Security Teams (FIRST), the
Common Vulnerability Scoring System (CVSS) is an "industry open standard
designed to convey vulnerability severity and help to determine urgency and
priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY
OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT
OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
http://www.auscert.org.au/render.html?cid=1980
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQIVAwUBVJIu5xLndAQH1ShLAQLNUQ//SsnjO5+8FzuGC0duwcJ9XtvFIh+ewTqj
WxVxYs3pzFaentMvNkQ6KW3uaENFp4az+FWghv3WCFmt/Aw8xA/eFXxCLlB02IKz
EALijgZKcCHNYDcfqqD3918gqsQwXQypKBCPNYp5x+MkPvtReDLE3pNE2X7eKN32
lHkXvKIL/oWj1ZEOdGBsFNipDLia97ijZaJqQNBuk4VvbADQkdfDkv+banDLovBd
UgVm3zeLNW2IYAZ7kvd750UpAin+v+DY1zDspTlNL/h8QOWt70cERM/HWw05dnf5
y1ts53K2hZD9kY8H2h/jGBgIDfmm35aARO+nBN24ocnGmgpfNmqGGJ00/TORDt7X
N2DSpnjAyEM+SsR6xtIHJPlEU/JZLOUVXQXLOijottqHdytA8OjPmgQvHrGcCuql
nsoyGV1QCl6B4ocBW/CyrVMeovcyZp5JyaiQb53JgWglVh8P904r3H1qaVpUtGYR
tnrcbpuI6v640KNfZTy3gR3AWMXxwBtQ+6bzWkaGeuy1bgeP9RXAWsV6iI/0gPdf
jaDfQImoUEWsEacWhZElK1JepAWtJgVYBB4rv7N/LHoRWE2esH9FmuUMVh8K1Gh1
jUX5nWv42sxY9oyWgwEdOdQ8A07pfyMsjpE/jB9JDIvLzwekrLV2Hhpf42Ev06U+
GZwhU6Gx9fY=
=ENd8
-----END PGP SIGNATURE-----