A flaw was found in all versions of kubeclient up to (but not including) v4.9.3, 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 Man-in-the-middle attacks (MITM).
github.com/ManageIQ/kubeclient
github.com/ManageIQ/kubeclient/commit/109ea71de5a8881748f03ebbe103b49f0f1c7887
github.com/ManageIQ/kubeclient/issues/554
github.com/ManageIQ/kubeclient/issues/555
github.com/ManageIQ/kubeclient/pull/556
github.com/rubysec/ruby-advisory-db/blob/master/gems/kubeclient/CVE-2022-0759.yml
nvd.nist.gov/vuln/detail/CVE-2022-0759