home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT06353 Status: Geschlossen

SECURITY: IBM DB2 contains a file disclosure vulnerability using a SELECT
statement with XML/XSLT function (CVE-2014-8910)

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
IBM DB2 contains a file disclosure vulnerability. A remote, 
authenticated DB2 user could exploit this vulnerability by 
issuing a specially-crafted XML statement to view text files 
owned by the DB2 instance owner.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 systems on all Linux, Unix and Windows platforms at  * 
* service levels Version 10.5 GA  through to Version 10.5 Fix  * 
* Pack 5.                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 6.                      * 
* Refer to security bulletin for details:                      * 
* http://www-01.ibm.com/support/docview.wss?uid=swg21697988    * 
****************************************************************
Local-Fix:
Lösung
First fixed in DB2 version 10.5 fix pack 6.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
07.01.2015
19.01.2016
19.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.6 FixList