Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-6758-979h-249x
No affected components available
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
- Tenant
solar, owned by a ServiceAccount namedtenant-ownerin the Namespacesolar - Tenant
wind, owned by a ServiceAccount namedtenant-ownerin the Namespacewind
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-proxyruns with the--disable-caching=false(default value:false)- Tenant owners are ServiceAccount, with the same resource name, but in different Namespaces.
The CVE doesn't allow any privilege escalation on the outer tenant Namespace-scoped resources, since the Kubernetes RBAC is enforcing this.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a low impact on the confidentiality of the information.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard