RHSA-2021:5137: Moderate: Openshift Logging Security Release (5.0.10)

Published Dec 14, 2021

Updated

Openshift Logging Bug Fix Release (5.0.10)<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> 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 Logging

Remediation

Event History

Mar 23, 2025

Advisory Published

via Red Hat·04:03 AM

Data Sourced

via Red Hat·04:03 AM

RemedyDescriptionAffected Software

Frequently Asked Questions

What is the severity of RHSA-2021:5137?

The severity of RHSA-2021:5137 is classified as moderate.

How do I fix RHSA-2021:5137?

To fix RHSA-2021:5137, update your OpenShift Logging to the version that addresses the log4j vulnerability.

What is CVE-2021-44228 in relation to RHSA-2021:5137?

CVE-2021-44228 is a vulnerability that allows remote code execution through maliciously crafted log strings in Log4j 2.x.

What software is affected by RHSA-2021:5137?

RHSA-2021:5137 affects OpenShift Logging components using log4j-core.

Is the log4j vulnerability in RHSA-2021:5137 critical?

The log4j vulnerability in RHSA-2021:5137 is considered serious but is classified as moderate in this specific release.

Company

Resources

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.