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 |
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 |
Configurations
History
21 Nov 2024, 06:39
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/ManageIQ/kubeclient/issues/554 - Issue Tracking, Patch, Third Party Advisory | |
References | () https://github.com/ManageIQ/kubeclient/issues/555 - Issue Tracking, Patch, Third Party Advisory |
Information
Published : 2022-03-25 19:15
Updated : 2024-11-21 06:39
NVD link : CVE-2022-0759
Mitre link : CVE-2022-0759
CVE.ORG link : CVE-2022-0759
JSON object : View
Products Affected
redhat
- kubeclient
CWE
CWE-295
Improper Certificate Validation