github.com/projectcapsule/capsule
Affected
- introduced
0, fixed0.4.5(semver)
Fixed versions
0.4.5
Fix
- Fixed version
0.4.5go get github.com/projectcapsule/[email protected]
Advisory
Also known as: CVE-2023-46254
capsule-proxy service discloses Namespaces of colliding tenants to owners of different tenants with the same ServiceAccount name
Summary
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.
Details
solar, owned by a ServiceAccount named tenant-owner in the Namespace solarwind, owned by a ServiceAccount named tenant-owner in the Namespace wind> Please, notice the same ServiceAccount name, although in different namespaces.
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:
capsule-proxy runs with the --disable-caching=false (default value: false)The CVE doesn't allow any privilege escalation on the outer tenant Namespace-scoped resources, since the Kubernetes RBAC is enforcing this.
Medium Basis: The source's own band: MODERATE
0, fixed 0.4.5 (semver)0.4.5
0.4.5go get github.com/projectcapsule/[email protected]0, fixed 0.4.5 (semver)0.4.5
0.4.5go get github.com/projectcapsule/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0