Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2022.0297
Security Bulletin: Vulnerability in Apache Log4j affects IBM
Cloud Private (CVE-2021-45046)
21 January 2022
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: IBM Cloud Private
Publisher: IBM
Operating System: Network Appliance
Impact/Access: Execute Arbitrary Code/Commands -- Remote/Unauthenticated
Denial of Service -- Remote/Unauthenticated
Resolution: Patch/Upgrade
CVE Names: CVE-2021-45105 CVE-2021-45046 CVE-2021-44228
Reference: ASB-2021.0244.6
Original Bulletin:
https://www.ibm.com/support/pages/node/6529452
https://www.ibm.com/support/pages/node/6529458
Comment: This bulletin contains two (2) IBM security advisories.
- --------------------------BEGIN INCLUDED TEXT--------------------
Vulnerability in Apache Log4j affects IBM Cloud Private (CVE-2021-45046)
Document Information
Document number : 6529452
Modified date : 18 January 2022
Product : IBM Cloud Private
Software version : all
Operating system(s): Linux
Summary
There is a vulnerability in the Apache Log4j open source library. The library
is used by Elasticsearch, a dependency of IBM Cloud Private, for logging
messages to files. This bulletin identifies the security fixes to apply to
address the Log4Shell vulnerability (CVE-2021-45046).
Vulnerability Details
CVEID: CVE-2021-45046
DESCRIPTION: Apache Log4j could result in remote code execution, caused by an
incomplete fix of CVE-2021-44228 in certain non-default configurations. When
the logging configuration uses a non-default Pattern Layout with a Context
Lookup, an attacker with control over Thread Context Map (MDC) input data can
craft malicious input data using a JNDI Lookup pattern to leak sensitive
information and remote code execution in some environments and local code
execution in all environments.
CVSS Base score: 9
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/
215195 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H)
Affected Products and Versions
+--------------------+----------+
|Affected Product(s) |Version(s)|
+--------------------+----------+
|IBM Cloud Private |3.1.0 |
+--------------------+----------+
|IBM Cloud Private |3.1.1 |
+--------------------+----------+
|IBM Cloud Private |3.1.2 |
+--------------------+----------+
|IBM Cloud Private |3.2.0 |
+--------------------+----------+
|IBM Cloud Private |3.2.1 CD |
+--------------------+----------+
|IBM Cloud Private |3.2.2 CD |
+--------------------+----------+
Remediation/Fixes
IBM strongly recommends addressing the vulnerability now by upgrading.
The recommended solution involves the IBM Cloud Private ibm-icplogging
component. It is recommended that you follow the instructions for the component
in the links listed below:
For IBM Cloud Private 3.1.0: IBM Cloud Private 3.1.0 Patch
For IBM Cloud Private 3.1.1: IBM Cloud Private 3.1.1 Patch
For IBM Cloud Private 3.1.2: IBM Cloud Private 3.1.2 Patch
For IBM Cloud Private 3.2.0: IBM Cloud Private 3.2.0 Patch
For IBM Cloud Private 3.2.1: IBM Cloud Private 3.2.1 Patch
For IBM Cloud Private 3.2.2: IBM Cloud Private 3.2.2 Patch
For IBM Cloud Private 3.1.0:
o Upgrade to the latest Continuous Delivery (CD) update package, IBM Cloud
Private 3.2.2.
Workarounds and Mitigations
None
Details of the ElasticSearch remediation for IBM Cloud Private Version 3.2.1
and 3.2.2
The ibm-icplogging component has been updated to use Elasticsearch 6.8.22. This
release upgrades the Log4j package to 2.17.0, which remediates the log4j
vulnerabilities and should not trigger false positives in vulnerability
scanners as was the case with Elasticsearch 6.8.21.
Elasticsearch announcement (ESA-2021-31)
https://discuss.elastic.co/t/
apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31
/291476
Details of the ElasticSearch remediation for IBM Cloud Private Version 3.1.1,
3.1.2, and 3.2.0
Elasticsearch and Logstash within ibm-icplogging component have been updated to
remediate the log4j vulnerabilities by removing the vulnerable JndiLookup class
from the log4j-core package. Some vulnerability scanners may continue to flag
Elasticsearch in association with this vulnerability based on the Log4j version
alone. However, the mitigation sufficiently protects both remote code execution
and information leakage.
Elasticsearch 5.0.0-5.6.10 and 6.0.0-6.3.2: Log4j CVE-2021-44228,
CVE-2021-45046 remediation
https://discuss.elastic.co/t/
elasticsearch-5-0-0-5-6-10-and-6-0-0-6-3-2-log4j-cve-2021-44228-cve-2021-45046-remediation
/292054
Logstash 5.0.0-6.8.20 and 7.0.0-7.16.0: Log4j CVE-2021-44228, CVE-2021-45046
remediation
https://discuss.elastic.co/t/
logstash-5-0-0-6-8-20-and-7-0-0-7-16-0-log4j-cve-2021-44228-cve-2021-45046-remediation
/292343
Acknowledgement
Change History
21 Dec 2021: Initial Publication
22 Dec 2021: Add patch links for 3.1.1, 3.1.2, 3.2.0
18 Jan 2022: Add patch link for 3.1.0
- --------------------------------------------------------------------------------
Vulnerability in Apache Log4j affects IBM Cloud Private (CVE-2021-45105)
Document Information
Document number : 6529458
Modified date : 18 January 2022
Product : IBM Cloud Private
Software version : all
Operating system(s): Linux
Summary
There is a vulnerability in the Apache Log4j open source library. The library
is used by Elasticsearch, a dependency of IBM Cloud Private, for logging
messages to files. This bulletin identifies the security fixes to apply to
address the Log4Shell vulnerability (CVE-2021-45105).
Vulnerability Details
CVEID: CVE-2021-45105
DESCRIPTION: Apache Log4j is vulnerable to a denial of service, caused by the
failure to protect from uncontrolled recursion from self-referential lookups. A
remote attacker with control over Thread Context Map (MDC) input data could
craft malicious input data that contains a recursive lookup to cause a
StackOverflowError that will terminate the process. Note: The vulnerability is
also called LOG4J2-3230.
CVSS Base score: 7.5
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/
215647 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
Affected Products and Versions
+--------------------+----------+
|Affected Product(s) |Version(s)|
+--------------------+----------+
|IBM Cloud Private |3.1.0 |
+--------------------+----------+
|IBM Cloud Private |3.1.1 |
+--------------------+----------+
|IBM Cloud Private |3.1.2 |
+--------------------+----------+
|IBM Cloud Private |3.2.0 |
+--------------------+----------+
|IBM Cloud Private |3.2.1 CD |
+--------------------+----------+
|IBM Cloud Private |3.2.2 CD |
+--------------------+----------+
Remediation/Fixes
IBM strongly recommends addressing the vulnerability now by upgrading.
The recommended solution involves the IBM Cloud Private ibm-icplogging
component. It is recommended that you follow the instructions for the component
in the links listed below:
For IBM Cloud Private 3.1.0: IBM Cloud Private 3.1.0 Patch
For IBM Cloud Private 3.1.1: IBM Cloud Private 3.1.1 Patch
For IBM Cloud Private 3.1.2: IBM Cloud Private 3.1.2 Patch
For IBM Cloud Private 3.2.0: IBM Cloud Private 3.2.0 Patch
For IBM Cloud Private 3.2.1: IBM Cloud Private 3.2.1 Patch
For IBM Cloud Private 3.2.2: IBM Cloud Private 3.2.2 Patch
For IBM Cloud Private 3.1.0:
o Upgrade to the latest Continuous Delivery (CD) update package, IBM Cloud
Private 3.2.2.
Workarounds and Mitigations
None
Details of the ElasticSearch remediation for IBM Cloud Private Version 3.2.1
and 3.2.2
The ibm-icplogging component has been updated to use Elasticsearch 6.8.22. This
release upgrades the Log4j package to 2.17.0, which remediates the log4j
vulnerabilities and should not trigger false positives in vulnerability
scanners as was the case with Elasticsearch 6.8.21.
Elasticsearch announcement (ESA-2021-31)
https://discuss.elastic.co/t/
apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31
/291476
Details of the ElasticSearch remediation for IBM Cloud Private Version 3.1.1,
3.1.2, and 3.2.0
Elasticsearch and Logstash within ibm-icplogging component have been updated to
remediate the log4j vulnerabilities by removing the vulnerable JndiLookup class
from the log4j-core package. Some vulnerability scanners may continue to flag
Elasticsearch in association with this vulnerability based on the Log4j version
alone. However, the mitigation sufficiently protects both remote code execution
and information leakage.
Elasticsearch 5.0.0-5.6.10 and 6.0.0-6.3.2: Log4j CVE-2021-44228,
CVE-2021-45046 remediation
https://discuss.elastic.co/t/
elasticsearch-5-0-0-5-6-10-and-6-0-0-6-3-2-log4j-cve-2021-44228-cve-2021-45046-remediation
/292054
Logstash 5.0.0-6.8.20 and 7.0.0-7.16.0: Log4j CVE-2021-44228, CVE-2021-45046
remediation
https://discuss.elastic.co/t/
logstash-5-0-0-6-8-20-and-7-0-0-7-16-0-log4j-cve-2021-44228-cve-2021-45046-remediation
/292343
Acknowledgement
Change History
21 Dec 2021: Initial Publication
22 Dec 2021: Add patch links for 3.1.1, 3.1.2, 3.2.0
18 Jan 2022: Add patch link for 3.1.0
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
https://www.auscert.org.au/bulletins/
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQIVAwUBYeo9/ONLKJtyKPYoAQirrg//bpdfTN8hmYgtK1aLPIdDys8IR59YJdVW
diCp5C1s4QmZ3Non4PysKq7vdF5i5La1BngfzZKzsWA55atHrnVXJWzkujHUw8mQ
qxk5u/MjN5hT5k7PL4wuQIhrNXulRFlTQmsbl2am3bH4H3SGad35MG/tliJJMF6V
2kLDr4GVrWC87AaTGd2aQoHHXSpePtYxnUqJk6VqHi3WVSv3cUU5KVbKl95xZG7k
Z/GIcBqBIXIFE0H5u1GLS/95zcLTrxz2UYv/kZIUKBoDGycSDjEMTKpVYjQCQH5C
Vl7Gpf+/1vF5rne5jq+5CNfMirXbJmrwDCCIDndS4IoqyJOsfORfMEQSTITqpUg3
E9mRSsOJb6xn+F1y29v7J8pKgswbAtz6oWLWlsSSxgjF1IH7S4+p7iDd2XrRuGNY
v2JV9AZacrWGmmyqc0CX1vihhsY4HaeRa0YSF/PjnACXChvbVkS25EfBbhke6RH9
82UwUfu3HEpRZVjbrL6jEin0u0OovGG/S0ZQosXhgk6Jbd2BSrzZOF68TvaqHWwg
SggVA66K0/3MXp0RCWNDVPSvT2YGfRcYw0vJVylvShexJONCs1lcqwMzx+ndvCEt
NOE7mBpQCSD6RP8mtKdQeZHWt2S31dBjnFuI4asITggx4Mh1NCGF5lXlYc4b7Lzg
Lh/UofmW9Yw=
=Ytfy
-----END PGP SIGNATURE-----