RHSA-2021:5106: Critical: OpenShift Container Platform 4.6.z security update

Published Dec 16, 2021
·
Updated

Red Hat OpenShift Container Platform is Red Hat's cloud computing<br>Kubernetes application platform solution designed for on-premise or private<br>cloud deployments.<br>Security Fix(es):<br><li> log4j-core: Remote code execution in Log4j 2.x when logs contain an attacker-controlled string value (CVE-2021-44228)</li> <li> log4j-core: DoS in log4j 2.x with thread context message pattern and context lookup pattern (incomplete fix for CVE-2021-44228) (CVE-2021-45046)</li> 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.

Affected Software

1 affected component
Red Hat OpenShift Container Platform>=4.6.0

Remediation

Event History

Jun 20, 2024
Advisory Published
via Red Hat·01:36 AM
Data Sourced
via Red Hat·01:36 AM
RemedyDescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of RHSA-2021:5106?

The severity of RHSA-2021:5106 is critical due to the potential for remote code execution in Log4j 2.x.

2

How do I fix RHSA-2021:5106?

To fix RHSA-2021:5106, update the log4j-core package to the latest version as recommended by Red Hat.

3

Which versions of Red Hat OpenShift are affected by RHSA-2021:5106?

RHSA-2021:5106 affects various versions of Red Hat OpenShift Container Platform that include log4j-core versions vulnerable to the specified remote code execution.

4

What is the impact of not addressing RHSA-2021:5106?

Failing to address RHSA-2021:5106 could allow an attacker to execute arbitrary code on the affected system.

5

Is there a workaround for RHSA-2021:5106?

While the recommended action is to update, if immediate patching is not possible, mitigating factors include limiting access to vulnerable log4j components and auditing logs for exploitation attempts.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203