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 IT04730 Status: Geschlossen

SECURITY: DB2 may terminate abnormally when issuing an ALTER TAB LE
statement with AUTO_REVAL set to IMMEDIATE (CVE-2014-6159).

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Under rare circumstances, an ALTER TABLE statement may cause the 
DB2 server to terminate abnormally if AUTO_REVAL is set to 
IMMEDIATE.
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 4.                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 5 or see "Local Fix"    * 
* portion for other suggestions.                               * 
* See security bulletin for more details:                      * 
* http://www-01.ibm.com/support/docview.wss?uid=swg21688051    * 
****************************************************************
Local-Fix:
Set database configuration parameter AUTO_REVAL to a value other 
than IMMEDIATE.
Lösung
The complete fix for this problem first appears in DB2 Version 
10.5 Fix Pack 5 and all the subsequent Fix Packs.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.10.2014
11.12.2014
11.12.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList