Capsule
Capsule: Tenant owner bypasses Capsule's forbidden namespace/service/node label and annotation enforcement
Capsule is a multi-tenancy and policy-based framework for Kubernetes. Prior to 0.13.7, ForbiddenListSpec.ExactMatch in pkg/api/forbidden_list.go sorts denied metadata keys case-insensitively and then uses sort.SearchStrings, which assumes byte-order sorting. When an administrator's forbidden list mixes capitalized and lowercase keys or otherwise has different case-insensitive and byte ordering, the binary search can return false for a key that is present. An authenticated tenant owner can then pass the missed key through api.ValidateForbidden and bypass configured namespace, Service, or delegated node metadata restrictions, potentially influencing cluster policies, network exposure, or scheduling outside the tenant boundary. Uniformly lowercase lists whose two orderings coincide are not affected. This issue is fixed in version 0.13.7.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.13.7
Fixed in 0.13.7
Mitigation
Upgrade capsule to 0.13.7 or later.
References
- Vendor advisory github.com/projectcapsule/capsule/security/adv…
- Patch github.com/projectcapsule/capsule/pull/1982
- Patch github.com/projectcapsule/capsule/commit/755ce…
1 more
- Release notes github.com/projectcapsule/capsule/releases/tag…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.