Описание
Capsule tenant owner with "patch namespace" permission can hijack system namespaces
Attack Vector
Then, let me briefly explain the reasons for the errors mentioned above: 1. The 'kubectl edit' command was used to patch the namespace, but this operation requires both 'get' and 'patch' permissions, hence the error. One should use methods like 'curl' to directly send a PATCH request; 2. The webhook does not intercept patch operations on 'kube-system' because 'kube-system' does not have an ownerReference.
Below are my detailed reproduction steps
- Create a test cluster
kind create cluster --image=kindest/node:v1.24.15 --name=k8s - Install the capsule
helm install capsule projectcapsule/capsule -n capsule-system --create-namespace - Create a tenant
- Create user alice
- Patch kube-system (The first command is executed in the current shell, while the 2nd and 3rd commands require a different shell window because the current shell is being used as a proxy.)
- Check the result
The kube-system is patched successfully.
Summary
The tenant-owner can patch any arbitrary namespace that has not been taken over by a tenant (i.e., namespaces without the ownerReference field), thereby gaining control of that namespace.
I would like to express my apologies once again. I have always been sincere in my research and communication, and I did not intend to disturb you on purpose.
Пакеты
github.com/projectcapsule/capsule
<= 0.7.0
0.7.1
Связанные уязвимости
Capsule is a multi-tenancy and policy-based framework for Kubernetes. In Capsule v0.7.0 and earlier, the tenant-owner can patch any arbitrary namespace that has not been taken over by a tenant (i.e., namespaces without the ownerReference field), thereby gaining control of that namespace. Version 0.7.1 contains a patch.