CyberRota Analysis
AI-GeneratedKubernetes users utilizing Capsule versions prior to 0.13.7 are vulnerable to a bypass in the ForbiddenListSpec.ExactMatch functionality, which incorrectly handles case sensitivity in denied metadata keys. This flaw allows authenticated tenant owners to circumvent namespace, Service, or delegated node metadata restrictions, potentially compromising cluster policies and increasing the risk of unauthorized access or exposure. Organizations using Capsule should prioritize upgrading to version 0.13.7 to mitigate this high-severity vulnerability.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
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.