Skip to content

Improper Certificate Validation in kubeclient

High severity GitHub Reviewed Published Mar 26, 2022 to the GitHub Advisory Database • Updated May 4, 2023

Package

bundler kubeclient (RubyGems)

Affected versions

< 4.9.3

Patched versions

4.9.3

Description

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

Published by the National Vulnerability Database Mar 25, 2022
Published to the GitHub Advisory Database Mar 26, 2022
Reviewed Mar 30, 2022
Last updated May 4, 2023

Severity

High
8.1
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Weaknesses

CVE ID

CVE-2022-0759

GHSA ID

GHSA-69p3-xp37-f692

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.