For OpenShift Container Platform 4.7 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.redhat.com/en/documentation/openshift_container_platform/4.7/html/release_notes/ocp-4-7-release-notes
For Red Hat OpenShift Logging 5.0, see the following instructions to apply
this update:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.7/html/logging/cluster-logging-upgrading
Openshift Logging Bug Fix Release (5.0.11)
Security Fix(es):
* 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.
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#low
An update is now available for OpenShift Logging (5.0.11)Red Hat Product Security has rated this update as having a security impactof Low. A Common Vulnerability Scoring System (CVSS) base score, whichgives a detailed severity rating, is available for each vulnerability fromthe CVE link(s) in the References section.
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://redhat.atlassian.net/jira/projects):
LOG-2075 - The elasticsearch-im-xxx job failed when trying to start index management process for a non-existent(empty-named) index
Get the latest Linux and open source security news straight to your inbox.