CVE-2022-0759
Published: 25 March 2022
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).
Priority
Status
Package | Release | Status |
---|---|---|
ruby-kubeclient Launchpad, Ubuntu, Debian |
impish |
Ignored
(end of life)
|
jammy |
Needs triage
|
|
upstream |
Needs triage
|
|
kinetic |
Ignored
(end of life, was needs-triage)
|
|
xenial |
Ignored
(end of standard support)
|
|
bionic |
Needs triage
|
|
focal |
Needs triage
|
|
trusty |
Ignored
(end of standard support)
|
|
mantic |
Needs triage
|
|
lunar |
Ignored
(end of life, was needs-triage)
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 8.1 |
Attack vector | Network |
Attack complexity | High |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | High |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
References
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0759
- https://bugzilla.redhat.com/show_bug.cgi?id=2058404
- https://github.com/ManageIQ/kubeclient/issues/554
- https://github.com/ManageIQ/kubeclient/pull/556
- https://github.com/ManageIQ/kubeclient/issues/555
- https://github.com/ManageIQ/kubeclient/pull/556
- NVD
- Launchpad
- Debian