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

高 8.8CVE-2022-46167 · GHSA-x45c-cvp8-q4fm · GO-2022-1135 · 02/12/2022 公開 · 17/06/2026 更新

要点

CVE-2022-46167 は github.com/clastix/capsule, capsule (clastix) に影響する深刻度「高」 (CVSS 8.8) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.94%（全脆弱性の 61.0% より高い）。
対処：0.1.3 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
github.com/clastix/capsule Go	`< 0.1.3`	`0.1.3`
capsule clastix	`< 0.1.3`	`0.1.3`

概要

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.

Patches

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

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

NVD の説明

Capsule is a multi-tenancy and policy-based framework for Kubernetes. Prior to version 0.1.3, 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. 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. Patches have been released for version 0.1.3. No known workarounds are available.