- Vulnerability/
- RHSA-2022:0318
RHSA-2022:0318: Moderate: Red Hat OpenShift distributed tracing 2.1.0 security update
First published: Thu Jan 27 2022(Updated: )
Release of Red Hat OpenShift distributed Tracing provides these changes:<br>Security Fix(es):<br><li> golang: net: incorrect parsing of extraneous zero characters at the beginning of an IP address octet (CVE-2021-29923)</li> <li> golang: net/http/httputil: panic due to racy read of persistConn after handler panic (CVE-2021-36221)</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.<br>The Red Hat OpenShift distributed tracing release notes provide information on<br>the features and known issues:<br><a href="https://docs.openshift.com/container-platform/latest/distr_tracing/distributed-tracing-release-notes.html" target="_blank">https://docs.openshift.com/container-platform/latest/distr_tracing/distributed-tracing-release-notes.html</a>
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat OpenShift Distributed Tracing |
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:0318?
The severity of RHSA-2022:0318 is considered to be significant due to the potential impact on applications using the affected Golang libraries.
How do I fix RHSA-2022:0318?
To fix RHSA-2022:0318, you should update your Red Hat OpenShift tracing components to the latest patched version provided in the advisory.
What vulnerabilities are addressed in RHSA-2022:0318?
RHSA-2022:0318 addresses vulnerabilities related to incorrect parsing of IP addresses and a panic scenario due to race conditions in Golang.
Which versions of Red Hat OpenShift are affected by RHSA-2022:0318?
RHSA-2022:0318 affects specific versions of Red Hat OpenShift that utilize the vulnerable Golang libraries.
Is there any workaround for RHSA-2022:0318?
There are no recommended workarounds for RHSA-2022:0318; applying the latest updates is the advised course of action.
- agent/severity
- agent/type
- agent/event
- agent/first-publish-date
- agent/last-modified-date
- collector/redhat-errata
- source/Red Hat
- anchor-id/RHSA-2022:0318
- agent/trending
- agent/title
- agent/remedy
- agent/references
- agent/description
- agent/source
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup