- Vulnerability/
- RHSA-2022:0043
RHSA-2022:0043: Low: Red Hat OpenShift Enterprise Logging security and bug fix update (5.2.5)
First published: Mon Jan 10 2022(Updated: )
Openshift Logging Bug Fix Release (5.2.5)<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:0043?
The severity of RHSA-2022:0043 is categorized as critical due to the potential denial of service vulnerability in log4j-core.
How do I fix RHSA-2022:0043?
You can fix RHSA-2022:0043 by updating log4j-core to the latest patched version provided in the advisory.
What vulnerability does RHSA-2022:0043 address?
RHSA-2022:0043 addresses the denial of service vulnerability CVE-2021-45105 in log4j-core.
Which software versions are affected by RHSA-2022:0043?
RHSA-2022:0043 affects Red Hat OpenShift Logging versions that utilize log4j-core.
Is there a workaround for RHSA-2022:0043?
There are no specific workarounds provided for RHSA-2022:0043, so applying the update is recommended.
- agent/severity
- agent/event
- agent/type
- agent/first-publish-date
- collector/redhat-errata
- source/Red Hat
- anchor-id/RHSA-2022:0043
- agent/last-modified-date
- agent/trending
- agent/references
- agent/title
- agent/remedy
- agent/description
- agent/source
- agent/tags
- agent/softwarecombine
- agent/guess-ai
- agent/software-canonical-lookup