DB2 - Problem description
Problem IT39918 | Status: Closed |
SECURITY: VERSION OF LIBEXPAT USED BY DB2 MAY ALLOW A REMOTE ATTACKER TO EXECUTE ARBITRARY CODE (CVE-2022-23852,CVE-2022-23990) | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
The version of libexpat used by Db2 could allow a remote attacker to execute arbitrary code caused by a buffer overflow (CVE-2022-23852,CVE-2022-23990). See Security Bulletin for details: https://www.ibm.com/support/pages/node/6573293 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All DB2 systems on all Linux, Unix and Windows platforms at * * service levels Version 11.1 GA through to Version 11.1 Fix * * Pack 6. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 11.1.4 Fix Pack 7 or higher. See * * Security Bulletin for details. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * All DB2 systems on all Linux, Unix and Windows platforms at * * service levels Version 11.1 GA through to Version 11.1 Fix * * Pack 6. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 11.1.4 Fix Pack 7 or higher. See * * Security Bulletin for details. * **************************************************************** | |
Comment | |
The complete fix for this problem first appears in DB2 Version 11.1.4.7 and all the subsequent Fix Packs. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.02.2022 19.04.2022 19.04.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |