A vulnerability in Apache Log4j could allow an attacker to execute arbitrary code on the system. This vulnerability may affect the IBM Spectrum Archive Enterprise Edition (EE). The below fix package includes Apache Log4j 2.15.
DESCRIPTION: Apache Log4j could allow a remote attacker to execute arbitrary code on the system, caused by the failure to protect against attacker controlled LDAP and other JNDI related endpoints by JNDI features. By sending a specially crafted code string, an attacker could exploit this vulnerability to load arbitrary Java code on the server and take complete control of the system. Note: The vulnerability is also called Log4Shell or LogJam.
CVSS Base score: 10
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/214921 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H)
Affected Products and Versions
|126.96.36.199 - 188.8.131.52
IBM strongly recommends addressing this vulnerability now by upgrading.
Note: The below fix package includes Log4j 2.15.
Workarounds and Mitigations
IBM strongly recommends addressing the vulnerability now by executing these manual steps, for Log4j in Elasticsearch and Logstash.
IBM Spectrum Archive Enterprise Edition includes three dependent software which include the version of Apache Log4j with the vulnerability described in CVE-2021-44228. They are
- HSM Component in IBM Spectrum Archive Enterprise Edition 184.108.40.206-220.127.116.11: Log4j 2.13.3
- Elasticsearch 5.6.8 in IBM Spectrum Archive Enterprise Edition 18.104.22.168-22.214.171.124: Log4j 2.9.1
- Logstash 5.6.8 in IBM Spectrum Archive Enterprise Edition 126.96.36.199-188.8.131.52: Log4j 2.6.2
HSM component is always installed by the default installation procedure of IBM Spectrum Archive Enterprise Edition, and Elasticsearch and Logstash RPMs are manually installed when the dashboard function is needed.
Fix for Log4j shipped with HSM component
Upgrade to the version described in Remediation/Fixes section.
Mitigation for Log4j bundled in Elasticsearch and Logstash
Logstash is typically installed under /usr/share/logstash directory on all IBM Spectrum Archive nodes when the dashboard function is used, and Elasticsearch is installed under /usr/share/elasticsearch directory on external monitoring server. Per the Apache Log4j security vulnerability advisory, find the Log4j jar files under those installation directories, and remove the JndiLookup class from the jar files by:
zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class See the security announcements and detailed instructions from Elastic for removing JndiLookup from relevant JAR files.
Get Notified about Future Security Bulletins
16 Dec 2021: Initial Publication
12 Jan 2022: Updated Remediation/Fixes section, with the fixing level 184.108.40.206
*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.
Review the IBM security bulletin disclaimer and definitions regarding your responsibilities for assessing potential impact of security vulnerabilities to your environment.
Was this topic helpful?
12 January 2022