A flaw was found in kubeclient, the Ruby client for Kubernetes REST API, in the way it parsed kubeconfig files. When the kubeconfig file does not configure custom CA to verify certs, kubeclient ends up accepting any certificate (it wrongly returns VERIFY_NONE). Ruby applications that leverage kubeclient to parse kubeconfig files are susceptible to MITM attacks.
Upstream patches. issues: https://github.com/ManageIQ/kubeclient/issues/554 + https://github.com/ManageIQ/kubeclient/issues/555 PRs: https://github.com/ManageIQ/kubeclient/pull/556 + https://github.com/ManageIQ/kubeclient/pull/557
Red Hat Satellite ships affected RubyGem Kubeclient, however, the product is not vulnerable, since it does not parse KubeClient through the affected "Kubeclient::Config" code. Therefore, we are reducing product impact to low.
This issue has been addressed in the following products: RHOL-5.4-RHEL-8 Via RHSA-2022:1461 https://access.redhat.com/errata/RHSA-2022:1461
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2022-0759
This issue has been addressed in the following products: OpenShift Logging 5.2 Via RHSA-2022:2218 https://access.redhat.com/errata/RHSA-2022:2218
This issue has been addressed in the following products: OpenShift Logging 5.3 Via RHSA-2022:2217 https://access.redhat.com/errata/RHSA-2022:2217
This issue has been addressed in the following products: RHOL-5.5-RHEL-8 Via RHSA-2022:6051 https://access.redhat.com/errata/RHSA-2022:6051