What is CVE-2022-0759?

CVE-2022-0759 is a high-severity security vulnerability in kubeclient (rubygems), affecting versions < 4.9.3. It is fixed in 4.9.3.

How severe is CVE-2022-0759?

CVE-2022-0759 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of kubeclient are affected by CVE-2022-0759?

kubeclient (rubygems) versions < 4.9.3 is affected.

Is there a fix for CVE-2022-0759?

Yes. CVE-2022-0759 is fixed in 4.9.3. Upgrade to this version or later.

Is CVE-2022-0759 exploitable, and should I be worried?

Whether CVE-2022-0759 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-0759 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2022-0759 in kubeclient

Q: How severe is CVE-2022-0759?

CVE-2022-0759 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of kubeclient are affected by CVE-2022-0759?

kubeclient (rubygems) versions < 4.9.3 is affected.

Q: Is there a fix for CVE-2022-0759?

Yes. CVE-2022-0759 is fixed in 4.9.3. Upgrade to this version or later.

Q: Is CVE-2022-0759 exploitable, and should I be worried?

Whether CVE-2022-0759 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-0759 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-0759?

Upgrade kubeclient to 4.9.3 or later.

Summary

Improper Certificate Validation in kubeclient

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).

Impact

CVE-2022-0759 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.9.3); upgrading removes the vulnerable code path.

Affected versions

kubeclient (< 4.9.3)

Security releases

kubeclient → 4.9.3 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade kubeclient to 4.9.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-0759? CVE-2022-0759 is a high-severity security vulnerability in kubeclient (rubygems), affecting versions < 4.9.3. It is fixed in 4.9.3.
How severe is CVE-2022-0759? CVE-2022-0759 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of kubeclient are affected by CVE-2022-0759? kubeclient (rubygems) versions < 4.9.3 is affected.
Is there a fix for CVE-2022-0759? Yes. CVE-2022-0759 is fixed in 4.9.3. Upgrade to this version or later.
Is CVE-2022-0759 exploitable, and should I be worried? Whether CVE-2022-0759 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-0759 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-0759? Upgrade kubeclient to 4.9.3 or later.