The Apache Log4j open source library used by IBM® Db2® is affected by a vulnerability that could allow a remote attacker to execute arbitrary code on the system. This library is used by the Db2 Federation feature. The fix for the vulnerability is to update the log4j library to version 2.17.1. Please see CVE-2021-4104 for bulletin relating to Log4j V1. Please see CVE-2021-45046, CVE-2021-45105 and CVE-2021-44228 for bulletins relating to Log4j V2.
DESCRIPTION: Apache Log4j could allow a remote attacker with permission to modify the logging configuration file to execute arbitrary code on the system. By constructing a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI , an attacker could exploit this vulnerability to execute remote code.
CVSS Base score: 6.6
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/216189 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H)
Affected Products and Versions
Fix pack levels of IBM Db2 V11.5 for all editions on all platforms are affected only if the following features are configured:
- DVM JDBC wrapper driver,
- NoSQL wrapper driver (for Hadoop),
- Blockchain wrapper driver (for Hyperledger Fabric, Linux 64-bit, x86-64 only)
IBM Db2 V9.7, V10.1, V10.5 and V11.1 are not affected by this issue. Please note that log4j v1.x was removed in a previous build, and customers are strongly recommended to apply those fixes if you are on an older version of Db2. See Security Bulletin for details.
To determine if Federation is enabled, issue the following:
db2 get dbm cfg | grep FEDERATED
If a value of NO is returned, you are not vulnerable.
You can determine if you are using one of the affected wrappers by performing:
To determine if the DVM JDBC wrapper is in use, issue the following statement:
db2 "select servername from syscat.serveroptions where option = 'DRIVER_CLASS' and setting = 'com.rs.jdbc.dv.DvDriver'"
If a servername is returned, then you are using the DVM JDBC wrapper via the DvDriver class.
To determine if the NoSQL hadoop wrapper is in use, issue the following statement:
db2 "select * from syscat.servers where servertype = 'HDFSPARQUET'"
If 1 or more rows are returned, then NoSQL hadoop wrapper is in use.
To determine if the NoSQL Blockchain wrapper is in use, issue the following statement:
db2 "select * from syscat.serveroptions where option='PEER_URL'"
If 1 or more rows are returned, then NoSQL Blockchain wrapper is in use.
Customers running any vulnerable fixpack level of an affected Program, V11.5, can download the special build containing the interim fix for this issue from Fix Central. These special builds are available based on the most recent fixpack level for the V11.5.6 and V11.5.7 release. They can be applied to any affected fixpack level of the appropriate release to remediate this vulnerability.
|Release||Fixed in fix pack||APAR||Download URL|
|V11.5||TBD||IT39584||Special Build for V11.5.6:|
|V11.5||TBD||IT39584||Special Build for V11.5.7:|
Workarounds and Mitigations
On a Unix-type system, if you are not using Federation wrappers, you can remove log4j jar files.
Get Notified about Future Security Bulletins
06 June 2022: Updated with links to related Log4j bulletins
08 Mar 2022: Updated to the correct link for Linux 64-bit, POWER little endian
24 Feb 2022: Added workaround note regarding removing log4j files when on a Unix-type system and Federation wrappers are not being used.
02 Feb 2022: Clarified versions impacted
28 Jan 2022: Added a clarification for releases not impacted.
24 Jan 2022: Initial Publication
*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.
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. In addition to other efforts to address potential vulnerabilities, IBM periodically updates the record of components contained in our product offerings. As part of that effort, if IBM identifies previously unidentified packages in a product/service inventory, we address relevant vulnerabilities regardless of CVE date. Inclusion of an older CVEID does not demonstrate that the referenced product has been used by IBM since that date, nor that IBM was aware of a vulnerability as of that date. We are making clients aware of relevant vulnerabilities as we become aware of them. "Affected Products and Versions" referenced in IBM Security Bulletins are intended to be only products and versions that are supported by IBM and have not passed their end-of-support or warranty date. Thus, failure to reference unsupported or extended-support products and versions in this Security Bulletin does not constitute a determination by IBM that they are unaffected by the vulnerability. Reference to one or more unsupported versions in this Security Bulletin shall not create an obligation for IBM to provide fixes for any unsupported or extended-support products or versions.
Was this topic helpful?
06 June 2022