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).
The product does not validate, or incorrectly validates, a certificate.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Kubeclient | Redhat | * | 4.9.3 (excluding) |
| Logging subsystem for Red Hat OpenShift 5.4 | RedHat | openshift-logging/fluentd-rhel8:v1.14.5-3 | * |
| OpenShift Logging 5.2 | RedHat | openshift-logging/fluentd-rhel8:v1.7.4-176 | * |
| OpenShift Logging 5.3 | RedHat | openshift-logging/fluentd-rhel8:v1.7.4-178 | * |
| Red Hat Satellite 6.14 for RHEL 8 | RedHat | rubygem-kubeclient-0:4.10.1-1.el8sat | * |
| RHOL-5.5-RHEL-8 | RedHat | openshift-logging/fluentd-rhel8:v1.14.6-29 | * |
| Ruby-kubeclient | Ubuntu | bionic | * |
| Ruby-kubeclient | Ubuntu | impish | * |
| Ruby-kubeclient | Ubuntu | kinetic | * |
| Ruby-kubeclient | Ubuntu | lunar | * |
| Ruby-kubeclient | Ubuntu | mantic | * |
| Ruby-kubeclient | Ubuntu | trusty | * |
| Ruby-kubeclient | Ubuntu | xenial | * |