What is CVE-2022-46167?

CVE-2022-46167 is a high-severity incorrect authorization vulnerability in github.com/clastix/capsule (go), affecting versions <= 0.1.2. It is fixed in 0.1.3. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.

How severe is CVE-2022-46167?

CVE-2022-46167 has a CVSS score of 8.8 (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 github.com/clastix/capsule are affected by CVE-2022-46167?

github.com/clastix/capsule (go) versions <= 0.1.2 is affected.

Is there a fix for CVE-2022-46167?

Yes. CVE-2022-46167 is fixed in 0.1.3. Upgrade to this version or later.

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

Whether CVE-2022-46167 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-46167 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-46167?

Upgrade github.com/clastix/capsule to 0.1.3 or later.

CVE-2022-46167 in github.com/clastix/capsule

Q: How severe is CVE-2022-46167?

CVE-2022-46167 has a CVSS score of 8.8 (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 github.com/clastix/capsule are affected by CVE-2022-46167?

github.com/clastix/capsule (go) versions <= 0.1.2 is affected.

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

Yes. CVE-2022-46167 is fixed in 0.1.3. Upgrade to this version or later.

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

Whether CVE-2022-46167 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-46167 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-46167?

Upgrade github.com/clastix/capsule to 0.1.3 or later.

Summary

Capsule vulnerable to privilege escalation by ServiceAccount deployed in a Tenant Namespace

Capsule implements a multi-tenant and policy-based environment in a Kubernetes cluster. A ServiceAccount deployed in a Tenant Namespace, when granted with PATCH capabilities on its own Namespace, is able to edit it and remove the Owner Reference, breaking the reconciliation of the Capsule Operator and removing all the enforcement like Pod Security annotations, Network Policies, Limit Range and Resource Quota items.

With that said, an attacker could detach the Namespace from a Tenant that is forbidding starting privileged Pods using the Pod Security labels by removing the OwnerReference, removing the enforcement labels, and being able to start privileged containers that would be able to start a generic Kubernetes privilege escalation.

Workarounds

N.A.

References

N.A.

For more information

If you have any questions or comments about this advisory:

Open an issue in github.com/clastix/capsule
Reach out on #capsule channel available on Kubernetes Slack workspace

Impact

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2022-46167 has a CVSS score of 8.8 (High). The vector is network-reachable, low 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 (0.1.3); upgrading removes the vulnerable code path.

Affected versions

github.com/clastix/capsule (<= 0.1.2)

Security releases

github.com/clastix/capsule → 0.1.3 (go)

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

Patches have been released for version 0.1.3 and all users must upgrade to this release.

Frequently Asked Questions

What is CVE-2022-46167? CVE-2022-46167 is a high-severity incorrect authorization vulnerability in github.com/clastix/capsule (go), affecting versions <= 0.1.2. It is fixed in 0.1.3. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
How severe is CVE-2022-46167? CVE-2022-46167 has a CVSS score of 8.8 (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 github.com/clastix/capsule are affected by CVE-2022-46167? github.com/clastix/capsule (go) versions <= 0.1.2 is affected.
Is there a fix for CVE-2022-46167? Yes. CVE-2022-46167 is fixed in 0.1.3. Upgrade to this version or later.
Is CVE-2022-46167 exploitable, and should I be worried? Whether CVE-2022-46167 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-46167 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-46167? Upgrade github.com/clastix/capsule to 0.1.3 or later.