- Vulnerability/
- RHSA-2022:0047
RHSA-2022:0047: Low: Red Hat OpenShift Enterprise Logging security and bug fix update (5.0.11)
First published: Mon Jan 10 2022(Updated: )
Openshift Logging Bug Fix Release (5.0.11)<br>Security Fix(es):<br><li> 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)</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 | Affected Version | How to fix |
|---|---|---|
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of RHSA-2022:0047?
The severity of RHSA-2022:0047 is classified as low due to the potential for denial of service.
How do I fix RHSA-2022:0047?
To fix RHSA-2022:0047, you should update to the latest version of OpenShift Logging that addresses the CVE-2021-45105 vulnerability.
What vulnerability does RHSA-2022:0047 address?
RHSA-2022:0047 addresses the CVE-2021-45105 vulnerability in log4j-core, which can lead to denial of service.
What software is affected by RHSA-2022:0047?
RHSA-2022:0047 affects OpenShift Logging deployments using vulnerable versions of log4j-core.
Is there a workaround for RHSA-2022:0047?
If updating is not possible, a temporary workaround may involve adjusting MDC input data handling to avoid the recursive lookup.
- agent/references
- agent/severity
- agent/event
- agent/type
- agent/first-publish-date
- collector/redhat-errata
- source/Red Hat
- anchor-id/RHSA-2022:0047
- agent/last-modified-date
- agent/remedy
- agent/title
- agent/description
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- agent/guess-ai
- agent/software-canonical-lookup