RHSA-2024:3621: Important: Red Hat OpenShift distributed tracing 3.2.0 operator/operand containers update
Important: Red Hat OpenShift distributed tracing 3.2.0 operator/operand containers update
Other sources
Release of Red Hat OpenShift distributed tracing provides these changes:Security Fix(es): go-resty: HTTP request body disclosure in github.com/go-resty/resty/v2 (CVE-2023-45286) golang: net/http: memory exhaustion in Request.ParseMultipartForm (CVE-2023-45290) golang: net/http/cookiejar: incorrect forwarding of sensitive headers and cookies on HTTP redirect (CVE-2023-45289) golang: crypto/x509: Verify panics on certificates with an unknown public key algorithm (CVE-2024-24783) golang: net/mail: comments in display names are incorrectly handled (CVE-2024-24784) golang: html/template: errors returned from MarshalJSON methods may break template escaping (CVE-2024-24785) golang-protobuf: encoding/protojson, internal/encoding/json: infinite loop in protojson.Unmarshal when unmarshaling certain forms of invalid JSON (CVE-2024-24786) golang: net/http, x/net/http2: unlimited number of CONTINUATION frames causes DoS (CVE-2023-45288) For more details about the security issue(s), including the impact, a CVSSscore, acknowledgments, and other related information, refer to the CVE page(s)listed in the References section.
— Red Hat
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2024:3621?
The severity of RHSA-2024:3621 is classified as Important.
How do I fix RHSA-2024:3621?
To fix RHSA-2024:3621, update your Red Hat OpenShift distributed tracing to the latest version that addresses the vulnerabilities.
What vulnerabilities are addressed in RHSA-2024:3621?
RHSA-2024:3621 addresses the HTTP request body disclosure issue in go-resty, identified as CVE-2023-45286.
Which products are affected by RHSA-2024:3621?
Affected products include Red Hat OpenShift distributed tracing for ARM, Power, IBM Z, and the standard Red Hat OpenShift distributed tracing.
What is the risk of not addressing RHSA-2024:3621?
Not addressing RHSA-2024:3621 may lead to potential exposure of sensitive HTTP request body data.