First published: Wed May 11 2022(Updated: )
Openshift Logging Bug Fix Release (5.2.10)<br>Security Fix(es):<br><li> kubeclient: kubeconfig parsing error can lead to MITM attacks (CVE-2022-0759)</li> <li> netty-codec: Bzip2Decoder doesn't allow setting size restrictions for decompressed data (CVE-2021-37136)</li> <li> netty-codec: SnappyFrameDecoder doesn't restrict chunk length and may buffer skippable chunks in an unnecessary way (CVE-2021-37137)</li> <li> netty: control chars in header names may lead to HTTP request smuggling (CVE-2021-43797)</li> <li> prometheus/client_golang: Denial of service using InstrumentHandlerCounter (CVE-2022-21698)</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 |
---|
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
RHSA-2022:2218 addresses vulnerabilities including a kubeconfig parsing error leading to MITM attacks (CVE-2022-0759) and a Bzip2Decoder restriction issue (CVE-2021-37136).
To fix the vulnerabilities associated with RHSA-2022:2218, you should update your OpenShift Logging to version 5.2.10 or later as recommended in the advisory.
The severity of RHSA-2022:2218 vulnerabilities ranges from moderate to high, particularly due to the potential for MITM attacks.
Yes, RHSA-2022:2218 specifically affects components related to kubeclient and netty-codec within OpenShift Logging.
Yes, an upgrade to OpenShift Logging version 5.2.10 is available to mitigate the vulnerabilities found in RHSA-2022:2218.