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).
References
Link | Resource |
---|---|
https://github.com/ManageIQ/kubeclient/issues/554 | Issue Tracking Patch Third Party Advisory |
https://github.com/ManageIQ/kubeclient/issues/555 | Issue Tracking Patch Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: redhat
Published: 2022-03-25T18:03:10
Updated: 2022-03-25T18:03:10
Reserved: 2022-02-24T00:00:00
Link: CVE-2022-0759
JSON object: View
NVD Information
Status : Analyzed
Published: 2022-03-25T19:15:10.283
Modified: 2022-04-07T19:13:51.897
Link: CVE-2022-0759
JSON object: View
Redhat Information
No data.
CWE