RHSA-2022:0042LowCVSS 5.9

Red Hat Security Advisory: Red Hat OpenShift Enterprise Logging security and bug fix update (5.1.6)

Published
January 10, 2022
Last Modified
August 4, 2026

🔗 CVE IDs covered (1)

CVE-2021-45105 →

📋 Description

CVE-2021-45105 — log4j-core: DoS in log4j 2.x with Thread Context Map (MDC) input data contains a recursive lookup and context lookup pattern

🎯 Affected products24

  • OpenShift Logging 5.1
  • openshift-logging/cluster-logging-operator-bundle@sha256:5aed9db163e965f2786e00f5cc27e2ae738a5ea400fde65403def07b56f9b44e_amd64 as a component of OpenShift Logging 5.1
  • openshift-logging/cluster-logging-rhel8-operator@sha256:49580fc09b09288cd708481e3d2a81e9fdcbd875d23e444a80a54d20165417d1_s390x as a component of OpenShift Logging 5.1
  • openshift-logging/cluster-logging-rhel8-operator@sha256:6628f6ce35760597d9ec97f6c5ffaca403728f0aac44f5d5d7d23f2c0a11911f_amd64 as a component of OpenShift Logging 5.1
  • openshift-logging/cluster-logging-rhel8-operator@sha256:ac41da9ee00bb755906009e21df87e586b7565a92f3b716fb99e72d744ef9ffe_ppc64le as a component of OpenShift Logging 5.1
  • openshift-logging/elasticsearch-operator-bundle@sha256:26cc3b0f2cf973f88251875484958a87c0184a26693385c5801edc0aa87b46ec_amd64 as a component of OpenShift Logging 5.1
  • openshift-logging/elasticsearch-proxy-rhel8@sha256:a68b9ed7b19e8289de0efce89bf0253b79703b46e4a0b54b7953202fea6f6513_s390x as a component of OpenShift Logging 5.1
  • openshift-logging/elasticsearch-proxy-rhel8@sha256:dbd6862307c3a4fc5c5ab67dbafb7be453ba3f1c7e914f2afc25bb817cb24b0e_amd64 as a component of OpenShift Logging 5.1
  • openshift-logging/elasticsearch-proxy-rhel8@sha256:e0116ef235fda9d4a07f10a9c5e8727daba6a9b7fb1b5aaa9ce5d870539ae1fe_ppc64le as a component of OpenShift Logging 5.1
  • openshift-logging/elasticsearch-rhel8-operator@sha256:2144ec2733a579ba4f6ff21f5a733f5ad52068ec7dc54252bbcbf38bdf9bde06_amd64 as a component of OpenShift Logging 5.1
  • openshift-logging/elasticsearch-rhel8-operator@sha256:757895d2dc77ffa86176a5a66b07e4a74306513a3b3bde9d66ba41b8a4cc2961_ppc64le as a component of OpenShift Logging 5.1
  • openshift-logging/elasticsearch-rhel8-operator@sha256:c1bb2b5fa69b561e3f65c262059a4784e1ac3d08afc05c1eac109a0b198f65d1_s390x as a component of OpenShift Logging 5.1
  • openshift-logging/elasticsearch6-rhel8@sha256:0bda3c71be7183afc13247ae55ca2f5b11193a82c8440a883aa73e403b5f77f6_ppc64le as a component of OpenShift Logging 5.1
  • openshift-logging/elasticsearch6-rhel8@sha256:74bc681d8c448a4bdff547b3f8119028e904c64c710fb1b5bb4ee016b13c2fdc_s390x as a component of OpenShift Logging 5.1
  • openshift-logging/elasticsearch6-rhel8@sha256:fef623d868f3c6f16d39f1853e236e52fbdf48f529b8fec4db21301d4fabecd5_amd64 as a component of OpenShift Logging 5.1
  • openshift-logging/eventrouter-rhel8@sha256:28f20684e4478a2a083039e5554ad364d764d3af9c07529b4c41b1feaed8183c_s390x as a component of OpenShift Logging 5.1
  • openshift-logging/eventrouter-rhel8@sha256:604e76ac4d6d562991adb4931b94cf499d9c06453c2f82376736ecae18495658_amd64 as a component of OpenShift Logging 5.1
  • openshift-logging/eventrouter-rhel8@sha256:cd4cb336303f187cec94043368fd30de9b79932fd29c2909fc08a623e4cc4c51_ppc64le as a component of OpenShift Logging 5.1
  • openshift-logging/fluentd-rhel8@sha256:ad2c3d7447af955402d903f83790f88d5f6d29cc523b54933c68d80366e5346e_s390x as a component of OpenShift Logging 5.1
  • openshift-logging/fluentd-rhel8@sha256:cf140d111408ed3cf2b245a6953de7fc1e958a1bfe18c430883fd95a612e4e6f_ppc64le as a component of OpenShift Logging 5.1
  • openshift-logging/fluentd-rhel8@sha256:dc891c8949a461c01dee41d9fff21a13b7ca9b7521c9be79363549bbf7fd6427_amd64 as a component of OpenShift Logging 5.1
  • openshift-logging/kibana6-rhel8@sha256:1aac827a9fb85bd9340c887790d9ef3577a77b8105a0f8fcd9897c603354450c_amd64 as a component of OpenShift Logging 5.1
  • openshift-logging/kibana6-rhel8@sha256:3cfa1f6fbe2374fe7393003f2bb1f1971d962398f7f4924e05837c54d4cacf06_ppc64le as a component of OpenShift Logging 5.1
  • openshift-logging/kibana6-rhel8@sha256:43e78035965f037c2d03060de332556fd996f91afef969dba80c90981e43ccd7_s390x as a component of OpenShift Logging 5.1

✅ Remediation

For OpenShift Container Platform 4.8 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.html For Red Hat OpenShift Logging 5.1, see the following instructions to apply this update: https://docs.openshift.com/container-platform/4.8/logging/cluster-logging-upgrading.html Workaround: For Log4j 2 versions up to and including 2.16.0, this flaw can be mitigated by: - In PatternLayout in the Log4j logging configuration, replace Context Lookups like ${ctx:loginId} or $${ctx:loginId} with Thread Context Map patterns (%X, %mdc, or %MDC) like %X{loginId}. - Otherwise, in the Log4j logging configuration, remove references to Context Lookups like ${ctx:loginId} or $${ctx:loginId} where they originate from sources external to the application such as HTTP headers or user input.

🔗 References (6)