Service accounts can see namespaces of other tenants in capsule-proxy
projectcapsule capsule-proxy
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/projectcapsule/capsule Go |
|
|
| github.com/projectcapsule/capsule-proxy Go |
|
|
projectcapsule capsule-proxy
| Product | Affected | Fixed in |
|---|---|---|
| github.com/projectcapsule/capsule Go |
|
|
| github.com/projectcapsule/capsule-proxy Go |
|
|
capsule-proxy is a reverse proxy for Capsule kubernetes multi-tenancy framework. A bug in the RoleBinding reflector used by `capsule-proxy` gives ServiceAccount tenant owners the right to list Namespaces of other tenants backed by the same owner kind and name. For example consider two tenants `solar` and `wind`. Tenant `solar`, owned by a ServiceAccount named `tenant-owner` in the Namespace `solar`. Tenant `wind`, owned by a ServiceAccount named `tenant-owner` in the Namespace `wind`. The Tenant owner `solar` would be able to list the namespaces of the Tenant `wind` and vice-versa, although this is not correct. The bug introduces an exfiltration vulnerability since allows the listing of Namespace resources of other Tenants, although just in some specific conditions: 1. `capsule-proxy` runs with the `--disable-caching=false` (default value: `false`) and 2. Tenant owners are ServiceAccount, with the same resource name, but in different Namespaces. This vulnerability doesn't allow any privilege escalation on the outer tenant Namespace-scoped resources, since the Kubernetes RBAC is enforcing this. This issue has been addressed in version 0.4.5. Users are advised to upgrade. There are no known workarounds for this vulnerability.
From the CVE record · GitHub_M
A bug in the capsule-proxy RoleBinding reflector lets a ServiceAccount tenant owner list Namespace resources belonging to another tenant. This requires capsule-proxy to run with --disable-caching=false and the tenants to have ServiceAccount owners with the same name in different Namespaces.
Teams running github.com/projectcapsule/capsule or github.com/projectcapsule/capsule-proxy versions earlier than 0.4.5 should check their deployments.