A Red Hat OpenShift Enterprise Logging bug fix and security update (5.3.2) has been released.

RHSA-2022:0044-06: Important: Red Hat OpenShift Enterprise Logging bug fix and security update (5.3.2)

=====================================================================
Red Hat Security Advisory

Synopsis: Important: Red Hat OpenShift Enterprise Logging bug fix and security update (5.3.2)
Advisory ID: RHSA-2022:0044-01
Product: Red Hat OpenShift Enterprise
Advisory URL:   https://access.redhat.com/errata/RHSA-2022:0044
Issue date: 2022-01-10
CVE Names: CVE-2020-36327 CVE-2021-3712 CVE-2021-20321
CVE-2021-42574 CVE-2021-45105
=====================================================================

1. Summary:

An update is now available for OpenShift Logging (5.3.2)

Red Hat Product Security has rated this update as having a security impact
of Important. A Common Vulnerability Scoring System (CVSS) base score,
which gives a detailed severity rating, is available for each vulnerability
from the CVE link(s) in the References section.

2. Description:

OpenShift Logging Bug Fix Release (5.3.2)

Security Fix(es):

* rubygem-bundler: Dependencies of gems with explicit source may be
installed from a different source (CVE-2020-36327)

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

For more details about the security issue(s), including the impact, a CVSS
score, acknowledgments, and other related information, refer to the CVE
page(s) listed in the References section.

3. Solution:

For OpenShift Container Platform 4.9 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.9/release_notes/ocp-4-9-release-notes.html

For Red Hat OpenShift Logging 5.3, see the following instructions to apply
this update:

  https://docs.openshift.com/container-platform/4.7/logging/cluster-logging-upgrading.html

4. Bugs fixed (  https://bugzilla.redhat.com/):

1958999 - CVE-2020-36327 rubygem-bundler: Dependencies of gems with explicit source may be installed from a different source
2034067 - 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

5. JIRA issues fixed (  https://issues.jboss.org/):

LOG-1975 - [release-5.3] After Upgrading to Cluster logging 5.3.0-55 receiving alerts Target Down `cluster-logging-operator`
LOG-2046 - [release-5.3] Wrong certificates used by fluentd when log forwarding to external Elasticsearch and defined structuredTypeKey
LOG-2051 - [release-5.3] Log collected dashboard displays wrong namespace
LOG-2074 - The elasticsearch-im-xxx job failed when trying to start index management process for a non-existent(empty-named) index [openshift-logging-5.3]
LOG-2088 - resourceVersion is overflowing type Integer causing ES rejection [openshift-logging 5.3]
LOG-2110 - [release-5.3] EO Self-generated certificates issue with Kibana when "logging.openshift.io/elasticsearch-cert-management: true" annotation is used

6. References:

  https://access.redhat.com/security/cve/CVE-2020-36327
  https://access.redhat.com/security/cve/CVE-2021-3712
  https://access.redhat.com/security/cve/CVE-2021-20321
  https://access.redhat.com/security/cve/CVE-2021-42574
  https://access.redhat.com/security/cve/CVE-2021-45105
  https://access.redhat.com/security/updates/classification/#important

7. Contact:

The Red Hat security contact is . More contact
details at   https://access.redhat.com/security/team/contact/

Copyright 2022 Red Hat, Inc.