Flashes (Alerts)
Abstract
This document contains a list of fixes for Security and HIPER APARs in DB2 Version 10.1.
IBM® recommends that the APAR descriptions be reviewed and one of the above fix packs to be deployed to correct them on the affected DB2 installations.
Content
A set of security vulnerabilities was discovered in some DB2 database products. These vulnerabilities were analyzed by the DB2 development organization and a set of corresponding fixes were created to address the reported issues. IBM is not currently aware of any externally reported incidents where production DB2 installations have been compromised due to these issues.
The affected DB2 UDB for Linux, UNIX, and Windows products are:
DB2 Enterprise Server Edition
DB2 Workgroup Server (all Editions)
DB2 Express Server (all Editions)
DB2 Personal Edition
DB2 Connect Server (all Editions)
DB2 Client component and DB2 products or components other than those listed above are not affected.
Due to the complexity of the fixes required to eliminate the reported service issues, it is not feasible to retrofit the same fixes into earlier DB2 Version 10.1 fix packs.
Select a Fix Pack: 6 | 5 | 4 | 3a | 3 | 2 | 1
DB2 Version 10.1 Fix Pack 6 | |||||
---|---|---|---|---|---|
Security APARs | |||||
IT07393 | SECURITY: DB2 ACS IS AFFECTED BY OPENSSL VULNERABILITY (CVE-2015-0204) | ||||
IT08751 | SECURITY: LOCAL ESCALATION OF PRIVILEGE VULNERABILITY IN DB2 (CVE-2015-1947) | ||||
IT09899 | SECURITY: GSKIT IS AFFECTED BY SECURITY VULNERABILITIES (CVE-2015-1788) | ||||
IT10083 | SECURITY: Multiple vulnerabilities in FCM affects DB2 (CVE-2015-1788 & CVE-2015-2808) | ||||
IT10087 | SECURITY: Multiple vulnerabilities in FCM affects DB2 (CVE-2015-4000) | ||||
IT11549 | SECURITY: DB2 IS AFFECTED BY SECURITY VULNERABILITIES IN IBM GPFS (CVE-2015-4974, CVE-2015-4981 & CVE-2015-7403) | ||||
IT12487 | SECURITY: DB2 SERVER MAY CRASH DUE TO MALFORMATTED DRDA MESSAGES (CVE-2016-0211) | ||||
IT12645 | SECURITY: GSKIT UPGRADE DUE TO SECURITY VULNERABILITIES (CVE-2015-7420, CVE-2015-7421 & CVE-2016-0201) | ||||
IT12669 | SECURITY: DB2 may trap when running query with AVG OLAP function on Oracle compatible database (CVE-2016-0215) | ||||
IT14999 | SECURITY: DB2 IS VULNERABLE TO THE DLL-PLANTING VULNERABILITY IN INSTALLSHIELD (CVE-2016-2542) | ||||
IT15485 | SECURITY: TABLE PRIVILEGE CHECKING MAY RETURN OUTDATED RESULTS AFTER A TABLE IS RENAMED (CVE-2017-1150) | ||||
IT15577 | SECURITY: DB2 IS AFFECTED BY OPEN SOURCE APACHE XERCES-C XML PARSER VULNERABILITIES (CVE-2016-0729) | ||||
IT16321 | SECURITY: DB2 PURESCALE AFFECTED BY MULTIPLE VULNERABILITIES IN GPFS | ||||
IT17011 | SECURITY: ELEVATED PRIVILEGES WITH DB2 EXECUTABLES (CVE-2016-5995) | ||||
IT17645 | SECURITY: VULNERABILITY IN GSKIT AFFECTS IBM DB2 (CVE-2016-2183) | ||||
HIPER APARs | |||||
IT03929 | DB2 MAY CRASH WHEN REPLAYING FEDERATED XA LOG RECORDS IF FEDERATED TWO_PHASE COMMIT IS USED | ||||
IT08989 | INCORRECT RESULT IS POSSIBLE IN FEDERATED ENVIRONMENT WHEN PLAN PUSHES DOWN FETCT FIRST N ROWS CLAUSE TO REMOTE SERVER | ||||
IT09390 | WRONG RESULTS MAY HAPPEN WHEN ACCESS PLAN CONTAINS INDEX SCAN ON THE OUTER LEG OF THE HASH JOIN | ||||
IT10059 | WRONG RESULTS USING AGGREGATION AND SAME COLUMN TWICE IN DIFFERENT AGGREGATION FUNCTIONS | ||||
IT10760 | INDEX/DATA MISMATCH MIGHT OCCUR IN AN MDC TABLE AFTER A DEFERRED ROLLOUT IS SUSPENDED | ||||
IT11604 | INDEX SCAN ON A DATA PARTITIONED TABLE MAY TRAP OR RETURN INCORRECT RESULTS IF PARTITIONS BECOME AVAILABLE DURING THE SCAN | ||||
IT11767 | DB2 MAY CRASH WITH SQLQGRFWDFEDPREP ON TOP OF CALL STACK WHEN REPLAYING FEDERATED XA LOG RECORDS | ||||
IT11774 | DB2 MIGHT PRODUCE INCORRECT RESULTS WHEN ELIMINATING CORRELATED SCALAR SUBQUERY | ||||
IT11870 | RECOVERING A FAILED ONLINE INCREMENTAL LOAD ON AN INDEX CREATED WITH THE "PCTFREE 0" OPTION MIGHT CORRUPT THE INDEX | ||||
IT12383 | ENABLING REOPT ALWAYS VIA OPTIMIZATION GUIDELINE MAY LEAD TO INCORRECT RESULTS AS PARAMETER VALUES MAY BE RE-USED INCORRECTLY | ||||
IT12567 | DB2 INSTANCE MAY ABEND WHEN CREATING COMPOUND STATEMENTS CONTAINING LIKE PREDICATES | ||||
IT13001 | VALUE FUNCTION WITH HASH JOIN MIGHT RETURN WRONG RESULT SET | ||||
IT13015 | TRUNCATE OF A DECLARED GLOBAL TEMPORARY TABLE MAY NOT RESULT IN TRUNCATED TABLE IN A PARTITIONED DATABASE | ||||
IT13193 | DB2 MIGHT PRODUCE INCORRECT RESULT WHEN EXECUTING QUERIES WITH INTERSECT AND DISTINCT | ||||
IT13266 | COMPILED TRIGGERS NOT FIRING AFTER UPGRADE FROM VERSION 9.7 TO 10.1 OR 10.5 | ||||
IT13321 | SQL STATEMENT CAN FAIL WITH SQL0901N OR PRODUCE WRONG RESULT WHEN ZZJOIN IS CHOSEN IN THE ACCESS PLAN | ||||
IT13347 | DB2 MIGHT PRODUCE INCORRECT RESULTS WHEN RUNNING QUERIES WITH EQUALITY TIMESTAMP PREDICATES | ||||
IT13415 | Query on Created Global Temporary Table MAY RETURN WRONG RESULTS IN DPF WHEN RUNNING THE SAME STATEMENT ON DIFFERENT PARTITIONS | ||||
IT13456 | COMPLEX XML QUERY GIVES INCORRECT RESULTS IN RARE CIRCUMSTANCES DUE TO INCORRECT PROCESSING OF PARTIALLY MATCHED ELEMENTS | ||||
IT13500 | INCORRECT RESULTS FROM SELECT ON INDEX CONTAINING MORE THAN 4,294,967,295 ROWS | ||||
IT13606 | DB2 ON AIX WITH DB2AUTH OR DB2_ALTERNATE_GROUP_LOOKUP SET MAY GET WRONG USER GROUP MEMBERSHIP RESULTING IN WRONG PRIVILEGES | ||||
IT14637 | IN FEDERATED SCENARIO, TABLE EXPRESSION AGAINST NICKNAME WITH BOTH CORRELATION AND FFNR CLAUSE COULD PRODUCE INCORRECT RESULT | ||||
IT14899 | SETTING THE FEDERATED SERVER OPTION DB2_REQUESTS_IO_BLOCK_BUF TO A HIGH VALUE CAN LEAD TO INCORRECT RESULTS BEING RETURNED | ||||
IT15056 | DB2 MIGHT PRODUCE INCORRECT RESULT WHEN EXECUTING QUERY WITH UNION AND MULTIPLE BASE TABLES | ||||
IT15312 | QUERIES CONTAINING MULTIPLE OUTER JOIN OPERATIONS AND NESTED EXPRESSIONS MAY PRODUCE INCORRECT RESULTS | ||||
IT15691 | DB2 SHORTCUTS DO NOT APPEAR POST INSTALLATION ON WINDOWS 2012 IF MICROSOFT SECURITY PATCH KB3126593 WAS APPLIED | ||||
IT16178 | IF ARRAY USED IN AN OPEN CURSOR IS MODIFIED WRONG RESULT OR A TRAP ARE POSSIBLE | ||||
IT16783 | SELECT ROW CHANGE TOKEN WILL RETURN WRONG RESULT WHEN USINGRIDSCAN (ROW IDENTIFIER SCAN) | ||||
IT17385 | INCORRECT QUERY RESULTS WHEN USING OFFSET-CLAUSE AND/OR FETCH-FIRST-CLAUSE | ||||
IT17453 | WRONG RESULT IN STORED PROCEDURE QUERY WHEN ADD/DROP CHECK CONSTRAINT | ||||
IT17488 | SELECT AGAINST MDC TABLE WITH A RANGE PREDICATE IN SMP MIGHT RETURN A WRONG RESULT | ||||
IT17506 | IN DB2 DPF, POSSIBLE WRONG RESULT WHEN OUTER JOIN PREDICATE COL1=COL2 AND BOTH COLUMNS ARE FROM THE OUTER TABLE | ||||
IT17790 | SQL STATEMENT WITH AN EXISTS PREDICATE AND A JOIN INVOLVING NON-DETERMINISTIC CORRELATED SUBQUERY MAY RETURN MORE ROWS | ||||
IT17851 | AN SQL STATEMENT IN A PARTITIONED DATABASE ENV CONTAINING THE ROW_NUMBER() OVER() OPERATION MIGHT PRODUCE INCONSISTENT RESULTS | ||||
IT17950 | POSSIBLE WRONG RESULTS WHEN THE INPUT PARAMETERS OF AN INLINED SQL SCALAR UDF CONTAINS AN OLAP SPECIFICATION | ||||
IT18019 | INCORRECTLY GENERATED DERIVED PREDICATES MIGHT CAUSE INCORRECT QUERY RESULTS DUE TO TRAILING BLANKS | ||||
IT18200 | WRONG RESULT IS POSSIBLE IF GENERATED ALWAYS EXPRESSION REFERENCES A BUILT-IN FUNCTION WITH MORE THEN ONE STRING INPUT | ||||
IT18203 | WRONG RESULT IS POSSIBLE IN ORACLE COMPATIBILITY MODE UNICODE DB WHEN COMPARING A CHAR COLUMN WITH A GRAPHIC CONSTANT | ||||
IT18380 | DB2 MAY RETURN INCORRECT RESULTS IF USING A CASE STATEMENT TO COMPARE FIXED CHAR/GRAPHIC STRINGS IN VARCHAR2 COMPATIBILITY MODE | ||||
IT18500 | DB2 CAN RETURN WRONG RESULTS WHEN USING THE SPECIAL REGISTER 'CURRENT DECFLOAT ROUNDING MODE' IN A QUERY IN AN MPP ENVIRONMENT | ||||
IT18515 | DB2 MAY RETURN SQLCODE:-901 OR RETURN WRONG RESULTS ON QUERIES WITH PLANS THAT INVOVLE SORT ON AN ENCRYPTED DATABASE | ||||
IT18760 | TRUNC ON MINIMUM INTEGER VALUE MIGHT RETURN 0 WHEN (VALUE, -X) IS DONE | ||||
IT18818 | WHEN RUNNING THE DYNAMIC SQL IN A PACKAGE, THE WRONG STATEMENT COULD BE PICKED UP, RESULTING IN WRONG RESULT | ||||
IT19196 | DB2 MIGHT PRODUCE INCORRECT RESULT WHEN EXECUTING XQUERY WITH MULTIPLE OR SUBTERMS | ||||
IT19297 | DB2 MIGHT PRODUCE INCORRECT RESULTS WHEN RUNNING QUERIES WITH EQUALITY CHAR/VARCHAR PREDICATES |
DB2 Version 10.1 Fix Pack 5 | |||||
---|---|---|---|---|---|
Security APARs | |||||
IT02593 | Security: DB2 contains a denial of service vulnerability in ALTER MODULE statement handling. (CVE-2014-309) | ||||
IT02646 | SECURITY: DB2 contains a denial of service vulnerability in SQL Compiler (CVE-2014-3095) | ||||
IT05652 | SECURITY: Multiple ALTER TABLE statements can cause DB2 to terminate (CVE-2014-6210). | ||||
IT05074 | SECURITY: DB2 may terminate abnormally when issuing an ALTER TABLE statement with AUTO_REVAL set to IMMEDIATE (CVE-2014-6159). | ||||
IT05647 | SECURITY: ALTER TABLE on an identity column may cause DB2 to terminate (CVE-2014-6209). | ||||
IT05939 | SECURITY: XML QUERY WILL CAUSE DB2 TO INCREASE CPU USAGE (CVE-2014-8901). | ||||
IT06350 | SECURITY: TLS padding vulnerability affects IBM® DB2® LUW (CVE-2014-8730) | ||||
IT06354 | SECURITY: INCORRECT EXTERNAL ENTITY HANDLING IN XML/XSLT (CVE-2014-8910) | ||||
IT07108 | SECURITY: DB2 TRAPS WHEN EXECUTING A SPECIALLY-CRAFTED SQL STATEMENT WITH SCALAR FUNCTIONS (CVE-2015-0157) | ||||
IT08080 | SECURITY: DB2 CONTAINS A FILE DISCLOSURE VULNERABILITY IN THE DATABASE AUTOMATED MAINTENANCE FEATURE (CVE-2015-1883) | ||||
IT07553 | SECURITY: DB2 contains a sensitive information exposure vulnerability in the monitoring and audit feature (CVE-2014-0919) | ||||
IT07646 | SECURITY: VULNERABILITIES IN GSKIT AFFECT IBM DB2 LUW (CVE-2015-0138) | ||||
IT08112 | SECURITY: DB2 IS AFFECTED BY MULTIPLE SECURITY VULNERABILITIES IN GPFS (CVE-2015-0197, CVE-2015-0198, CVE-2015-0199) | ||||
IT08525 | SECURITY: DB2 USER CAN DELETE TABLE DATA WITHOUT APPROPRIATE PRIVILEGES (CVE-2015-1922) | ||||
IT08536 | SECURITY: VULNERABILITY IN RC4 STREAM CIPHER AFFECTS IBM® DB2® LUW (CVE-2015-2808) | ||||
IT08543 | SECURITY: DB2 LUW CONTAINS A VULNERABILITY IN SCALAR FUNCTION THAT MAY CAUSE DB2 SERVER TO TERMINATE ABNORMALLY (CVE-2015-1935) | ||||
HIPER APARs | |||||
IC99978 | CLI-BASED APPLICATIONS RECEIVE SQL0501N AGAINST DB2 Z/OS WHEN STORED PROCEDURE CALL HAS MULTIPLE CURSORS | ||||
IT00392 | REPLAY OF REORG-INDEX-RECLAIM-EXTENTS LOG RECORDS MIGHT LEAD TO INDEX CORRUPTION | ||||
IT02046 | ACCESS PLANS CONTAINING INDEX ORING BETWEEN MDC AND NON MDC INDEX MAY NOT FETCH ALL ROWS FROM SECOND EXECUTION ONWARDS | ||||
IT03188 | INSERT MIGHT NOT RESPOND OR BE VERY SLOW OR HANG ON PURESCALE SYSTEMS | ||||
IT03929 | DB2 MAY CRASH WHEN REPLAYING FEDERATED XA LOG RECORDS IF FEDERATED TWO_PHASE COMMIT IS USED | ||||
IT04085 | WRONG RESULTS RECEIVED FOR A QUERY DUE TO INCORRECT INTERNAL COLUMN STRUCTURES | ||||
IT04236 | SQL STATEMENT WITH REPARTITIONED JOINS MIGHT RETURN INCORRECT RESULTS IN A DPF SYSTEM | ||||
IT04394 | INCORRECT QUERY RESULTS OR SQL0901N REASON "BAD OUTER COMPARE" POSSIBLE IN DPF WHEN SQL PLAN HAS MDTQ AND MERGE JOIN LOLEPOPS | ||||
IT04520 | INCORRECT RESULTS MIGHT BE PRODUCED IF HSJOIN HAS 2 NLJNs ON THE PROBE SIDE AND HSJN PROBE PUSH DOWN INTO THE SECOND NLJN DONE | ||||
IT05401 | IN A RARE CONDITION, A QUERY OF A CHAIN OF EQUALITY JOIN PREDICATES BETWEEN 4 OR MORE TABLES COULD PRODUCE EXTRA ROWS | ||||
IT05462 | INCORRECT RESULTS MIGHT BE RETURNED FOR A QUERY INVOLVING AN AGGREGATION FUNCTION AND AN OUTER JOIN OPERATOR | ||||
IT05891 | SQL STATEMENT WITH MULTIPLE SIMILAR CORRELATED SUBEXPRESSIONS MIGHT RETURN INCORRECT RESULTS | ||||
IT05940 | POTENTIAL CORRUPTION DURING READAHEAD DATA PREFETCHING WHEN A DECIMAL KEY PART IS USED WITH INDEX COMPRESSION | ||||
IT07562 | IN RARE SCENARIOS COMPLEX QUERY WITH AN OLAP SPECIFICATION AND A SUBQUERY MIGHT RETURN EXTRA ROWS | ||||
IT08235 | INCORRECT RESULT COULD BE RETURNED WHEN USING FULLWIDTH UNDER-SCORE CHARACTER (X'EFBCBF') IN LIKE PREDICATE AGAINST CLOB DATA | ||||
IT08504 | INCORRECT RESULT WHEN QUERY HAS LEFT OUTER JOIN AND UNION ALL | ||||
IT08551 | INGEST: SQL0804N OR INCORRECT DECIMAL DATA LOADED WHEN DECIMAL IS IN ASCII AND PRECISIONS DO NOT MATCH | ||||
IT08988 | HADR STANDBY LOG REPLAY OR ROLLFORWARD RECOVERY CAN FAIL DUE TO SQLB_BAD_PAGE | ||||
IT09137 | WRONG RESULT FROM STATEMENT WITH TWO OR MORE OLAP FUNCTIONS WITH COMPATIBLE PARTITION-BY CLAUSES WITH ONE EQUATING TO CONSTANTS | ||||
IT09595 | SYSIBM.POWER ( EXPRESSION1, EXPRESSION2 ) WILL RETURN INCORRECT RESULTS FOR SOME VALUES WHEN THE BIGINT DATA TYPE IS USED | ||||
IT09606 | SELECT ON XML USING FN:UPPER-CASE & TABLE HAS AN INDEX CAN RETURN INCORRECT RESULTS | ||||
IV64314 | WHEN INTRA_PARALLEL ENABLED, SQL STATEMENT WITH IN PREDICATE MIGHT RETURN INCORRECT RESULTS |
DB2 Version 10.1 Fix Pack 4 | |||||
---|---|---|---|---|---|
Security APARs | |||||
IC90397 | SECURITY: MULTIPLE GSKIT VULNERABILITIES IN IBM DB2 (CVE-2012-2190, CVE-2012-2191, CVE-2012-2203, CVE-2013-0169). | ||||
IC97471 | SECURITY: NULL POINTER DEREFERENCE IN DB2'S XSLT PARSING ENGINE (CVE-2013-5466). | ||||
IC97737 | SECURITY: QUERY WITH OLAP SPECIFICATION CAUSES DB2 SERVER TO SHUTDOWN DATABASE. (CVE-2013-6717) | ||||
IC99475 | Security: IBM DB2 is impacted by multiple TLS/SSL security vulnerabilities (CVE-2013-6747, CVE-2014-0963) | ||||
IC99480 | SECURITY: VULNERABILITY IN STORED PROCEDURE INFRASTRUCTURE CAN ALLOW ESCALATION OF PRIVILEGE TO ADMINISTRATOR (CVE-2013-6744). | ||||
IT00686 | SECURITY: ELEVATED PRIVILEGES WITH DB2 EXECUTABLES (CVE-2014-0907) | ||||
HIPER APARs | |||||
IC95046 | THE DBMS_LOB.COMPARE FUNCTION AND DBMS_LOB.READ PROCEDURE DO NOT PROCESS CLOBS CORRECTLY IF MULTI-BYTE CHARACTERS ARE PRESENT | ||||
IC96725 | CASE EXPRESSION PREDICATES MIGHT BE INCORRECTLY REWRITTEN in DB2 v10.1 Fixpack 3 | ||||
IC89288 | QUERIES WITH THE XMLTABLE FUNCTION MIGHT RETURN INCORRECT RESULTS | ||||
IC97379 | THE ROUND FUNCTION WITH A MINIMUM VALUE FOR INTEGER AND BIGINT VALUES IS NOT RETURNING THE CORRECT RESULTS | ||||
IC97775 | INSTANCE MIGHT ABEND OR RETURN INCORRECT RESULTS DUE TO AN INCORRECT EXECUTION SECTION FOR STAR JOIN | ||||
IC97793 | INCORRECT RESULT IN UNICODE DB WITH LIKE PREDICATE AND FULLWIDTH UNDERSCORE WILD CHARACTER ON A CLOB COLUMN | ||||
IC97897 | UNEXPECTED LOCK ESCALATIONS ON DB2 PURESCALE SYSTEMS USING STMM LOCKLIST TUNING OR MANUAL DYNAMIC UPDATE OF LOCKLIST SETTING | ||||
IC98114 | IN DB2 DPF ENVIRONMENTS ONLY, A SPECIFIC TYPE OF QUERY AND RESULTING ACCESS PLAN MIGHT RETURN WRONG RESULTS | ||||
IC98129 | POSSIBLE INCORRECT RESULT ON MULTIPLE OUTER JOINS AND A COMBINATION OF EQUALITY JOIN PREDICATES AND LOCAL PREDICATES | ||||
IC98349 | A QUERY WITH AN OR PREDICATE MIGHT RETURN INCORRECT RESULTS | ||||
IC98361 | QUERY USING ZIGZAG IN THE ACCESS PLAN MIGHT PRODUCE WRONG RESULTS WHEN IN2JOIN IS IN THE ACCESS PLAN AS WELL. | ||||
IC98683 | ROWS MISSING WHEN LARGE RESULT SET IS PRODUCED BY NULLS FIRST SORT ON INTEGER OR BIGINT | ||||
IC99319 | SQL STATEMENT WITH ORDERED COLUMN GROUP OR PREDICATES MIGHT RETURN INCORRECT RESULT SET WHEN JUMP SCAN USED | ||||
IC99818 | SQL STATEMENT WITH UNCORRELATED SUBQUERY PREDICATE MIGHT RETURN INCORRECT RESULTS WHEN INTRA_PARALLEL IS ENABLED | ||||
IC99860 | POSSIBLE WRONG RESULTS WHEN INDEX JUMP SCANS ARE USED IN REFERENTIAL INTEGRITY CHECKING | ||||
IT00248 | QUERIES WITH XMLTABLE FUNCTIONS MIGHT RETURN INCORRECT RESULTS WHEN MORE THAN ONE EQUAL PREDICATE IS USED IN WHERE CLAUSE | ||||
IT00386 | SQL QUERY CONTAINS NOT EXISTS SUBQUERY AND NODENUMBER PREDICATE MIGHT PRODUCE AN INCORRECT RESULT | ||||
IT00423 | POTENTIAL INDEX CORRUPTION WHEN USING INDEX COMPRESSION AND UNICDOE DATABASES WHICH USE UCA COLLATION WITH S(STRENGTH) = 1 OR 2 | ||||
IT00929 | COLLATION_KEY_BIT MIGHT GENERATE EMPTY STRINGS IN ORACLE MODE IF INPUT STRING CONSISTS OF BLANKS | ||||
IT01073 | INCORRECT RESULTS MIGHT BE PRODUCED WITH PREDICATES INVOLVING NULL CONSTANTS | ||||
IT01100 | CHAR(' ',0) RETURNS EMPTY STRING INSTEAD OF NULL IN VARCHAR2 ENABLED DATABASE. | ||||
IT01189 | TABLE SPACE ROLLFORWARD MIGHT NOT UNDO TRANSACTION CORRECTLY, LEAVING INCONSISTENT DATA | ||||
IT01197 | QUERY MIGHT HAVE OR PREDICATE WRONGLY REMOVED RESULTING IN EXTRA ROWS IN THE RESULTS |
DB2 Version 10.1 Fix Pack 3a | |||||
---|---|---|---|---|---|
Security APARs | |||||
IC97471 | SECURITY: NULL POINTER DEREFERENCE IN DB2'S XSLT PARSING ENGINE (CVE-2013-5466). | ||||
IC97737 | SECURITY: QUERY WITH OLAP SPECIFICATION CAUSES DB2 SERVER TO SHUTDOWN DATABASE. (CVE-2013-6717) | ||||
IC99475 | Security: IBM DB2 is impacted by multiple TLS/SSL security vulnerabilities (CVE-2013-6747, CVE-2014-0963) | ||||
IC99480 | SECURITY: VULNERABILITY IN STORED PROCEDURE INFRASTRUCTURE CAN ALLOW ESCALATION OF PRIVILEGE TO ADMINISTRATOR (CVE-2013-6744). | ||||
IT00686 | SECURITY: ELEVATED PRIVILEGES WITH DB2 EXECUTABLES (CVE-2014-0907) |
DB2 Version 10.1 Fix Pack 3 | |||||
---|---|---|---|---|---|
Security APARs | |||||
IC92498 | SECURITY: STACK BUFFER OVERFLOW VULNERABILITY IN DB2AUD AND DB2FLACC (CVE-2013-3475). | ||||
IC94434 | SECURITY: DENIAL OF SERVICE VULNERABILITY IN DB2's FAST COMMUNICATIONS MANAGER. (CVE-2013-4032) | ||||
IC94757 | SECURITY: UNAUTHORIZED ACCESS TO TABLE VULNERABILITY IN DB2 (CVE-2013-4033) | ||||
HIPER APARs | |||||
IC89288 | INDEX CORRUPTION MIGHT BE INTRODUCED DURING A DATABASE UPGRADE TO DB2 VERSION 10.1 | ||||
IC89415 | READ STABILITY ISOLATION IS NOT ENFORCED UNDER CERTAIN SQL ACCESS PLANS | ||||
IC89818 | INCORRECT RESULTS ON RANGE PARTITIONED TABLE WITH XML COLUMN | ||||
IC90798 | INCORRECT RESULTS MIGHT BE RETURNED FOR THE SELECT QUERY INVOLVING THE AGGREGATION FUNCTION WITH THE OLAP WINDOW FUNCTION | ||||
IC90906 | A QUERY INVOLVING AT LEAST TWO COUNT(DISTINCT ...) AGGREGATE FUNCTIONS MIGHT RETURN WRONG RESULTS | ||||
IC91418 | USER-DEFINED FUNCTION WITH INDEX EXTENSION EXPLOITATION MIGHT RETURN INCORRECT RESULTS IF INDEX IS NOT PRESENT | ||||
IC92052 | EXCESSIVELY LARGE MEMORY ALLOCATION ATTEMPTS FROM FAST INTEGER SORT DUE TO WRONG MEMORY SIZE CALCULATION | ||||
IC92832 | FAILED BACKUP, TABLESPACES ARE MARKED AS UNMODIFIED, DATA MIGHT NOT BE INCLUDED IN SUBSEQUENT INCREMENTAL BACKUPS IMAGES | ||||
IC92990 | INDEX / DATA MISMATCH MIGHT OCCUR IN AN MDC TABLE AFTER A DEFERRED ROLLOUT | ||||
IC93059 | RANGE PARTITIONED TABLES DEFINED WITH A NULLS FIRST PARTITIONING COLUMN MIGHT RETURN INCORRECT RESULTS | ||||
IC93092 | UPDATE OF UNIQUE COLUMNS MIGHT RESULT IN DUPLICATES IN A TABLE WITH A UNIQUE INDEX | ||||
IC94252 | TCP CONNECTIONS FROM NON-HADR DATABASE SOFTWARE TO THE STANDBY MIGHT ALTER THE HADR STATE AND STALL LOG SHIPPING ON THE PRIMARY | ||||
IC94465 | BITWISE SCALAR FUNCTIONS MIGHT RETURN INCORRECT RESULTS WHEN USED WITH DECFLOAT DATATYPE ON AIX POWER7 | ||||
IC94634 | THERE MIGHT BE A DOUBLE FREE OR LIST CORRUPTION IN THE SQLRLC_CSM_DEFUNCT() FUNCTION | ||||
IC95010 | THE LOAD COMMAND WITH THE REMOTE FETCH OR SOURCEUSEREXIT OPTIONS MIGHT FAIL TO INSERT SOME ROWS INTO A TABLE | ||||
IC95053 | THE QUERY STATEMENT WITH A SUBQUERY PREDICATE MIGHT NOT RETURN ROWS AFTER ENABLING DB2_COMPATIBILITY_VECTOR=ORA |
DB2 Version 10.1 Fix Pack 2 | |||||
---|---|---|---|---|---|
Security APARs | |||||
IC86783 | SECURITY: STACK BUFFER OVERFLOW VULNERABILITY IN SQL/PERSISTENT STORED MODULES DEBUGGING INFRASTRUCTURE (CVE-2012-4826). | ||||
HIPER APARs | |||||
IC85608 | XQUERY MIGHT RETURN INCORRECT RESULTS WHEN BOTH 'AND' AND 'OR' PREDICATES EXIST AND ALL PREDICATES CAN BE APPLIED TO XML INDEXES | ||||
IC87500 | ROWS MIGHT BE INSERTED INTO WRONG MDC TABLE CELL AFTER PREVIOUS INSERTS IN SAME TRANSACTION ENCOUNTER TABLESPACE FULL | ||||
Special Attention APARs | |||||
IC85425 | QUERY WITH A UNION AND TWO CORRELATED BRANCHES MIGHT RETURN INCORRECT RESULTS IN PARTITIONED DATABASE ENVIRONMENTS | ||||
IC85841 | BATCH INSERTS CAUSING DUPLICATE ROWS WHEN USING NULLIDRA (REOPT=ALWAYS) VS. NULLIDR1 (REOPT=ONCE) | ||||
IC86029 | CREATING A UNIQUE GLOBAL INDEX ON A TABLE WITH DETACHED PARTITION AND DEPENDANT MQT MIGHT LEAD TO INCORRECT RESULT AFTER REFRESH |
DB2 Version 10.1 Fix Pack 1 | |||||
---|---|---|---|---|---|
Security APARs | |||||
IC84716 | SECURITY: SQLJ.DB2_INSTALL_JAR DIRECTORY ESCAPE VULNERABILITY (CVE-2012-2194). | ||||
IC84751 | SECURITY: GET_WRAP_CFG_C AND GET_WRAP_CFG_C2 ALLOWS UNAUTHORIZED ACCESS XML FILES (CVE-2012-2196). | ||||
IC84755 | SECURITY: STACK BUFFER OVERFLOW VULNERABILITY IN JAVA STORED PROCEDURE INFRASTRUCTURE (CVE-2012-2197). | ||||
IC85513 | SECURITY: UTL_FILE could allow unauthorized access to files (CVE-2012-3324). | ||||
HIPER APARs | |||||
IC83823 | WITH REOPT ENABLED, STATEMENTS CONTAINING ARRAY OR ROW VARIABLES MIGHT PRODUCE INCORRECT OUTPUT | ||||
IC84300 | DATABASE CORRUPTION UPON REACHING PHYSICAL LIMITS OF SMS TABLE SPACE | ||||
IC84320 | COALESCE EXPRESSION IN THE OUTER JOIN OPERATOR (+) MAY RETURN INCORRECT RESULTS | ||||
Special Attention APARs | |||||
IC83469 | INCORRECT RESULTS AFTER LOAD INTO TABLE WITH CONSTRAINTS FOLLOWED BY ATTACH OR DETACH | ||||
IC84856 | INDEX CORRUPTION MAY BE INTRODUCED DURING A DATABASE UPGRADE FROM DB2 VERSION 9.5 TO DB2 VERSION 10.1 | ||||
IC84899 | DATABASE OPERATIONS MIGHT FAIL WITH "KEY DATA MISMATCH" ERRORS, OR ROWS THAT EXIST IN THE DATABASE CANNOT BE FOUND | ||||
IC85221 | SQL WITH NESTED MATH OPERATIONS ON COLUMNS THAT ARE DEFINED WITH NOT NULL AND USING FUNCTIONS MAY RETURNED DIFFERENT RESULTS. |
DB2 fix packs for all supported versions can be downloaded at the following site: http://www.ibm.com/support/docview.wss?uid=swg27007053
The DB2 team will continue to have a strong focus on delivering timely fixes for newly discovered issues along with information that helps our customers to decide on an appropriate course of action. DB2 team regrets the inconvenience that these issues are causing to customers. DB2 team believes that their actions are the most prudent steps to address customer concerns and remain open to suggestions on how to further improve our processes.
My Notifications
Sign-up to receive e-mail notification of changes to this document.
- 1. Sign in to My Notifications
2. select Subscribe tab
3. select "Information Management" from the Software column
4. select the check box for "DB2 for Linux, UNIX and Windows"
click the Continue button.
5. select the check box for "Flashes" and all other document types
click the Submit button.
For more information about My Notifications please click on
- the Benefits and features or
- take an guided tour of My Notifications.
Was this topic helpful?
Document Information
Modified date:
25 September 2022
UID
swg21610582