نسخههای متأثر
بازهها نیاز به بررسی دارند.
- نسخههای متأثر
- <= 1.0.0
- نسخهٔ اصلاحشده
- اعلام نشده
- نسخههای متأثر
- *
- نسخهٔ اصلاحشده
- اعلام نشده
بهرهبرداری
شرح آسیبپذیری
Summary
Using an "open at the top" range definition in RBAC for etcd roles leads to some TCPs API servers being able to read, write and delete the data of other control planes.
Details
The problematic code is this: https://github.com/clastix/kamaji/blob/8cdc6191242f80d120c46b166e2102d27568225a/internal/datastore/etcd.go#L19-L24
The range created by this RBAC setup code looks like this:
etcdctl role get example
Role example
KV Read:
[/example/, \0)
KV Write:
[/example/, \0)
The range end \0 means "everything that comes after" in etcd, so potentially all the key prefixes of controlplanes with a name that comes after "example" when sorting lexically (e.g. example1, examplf, all the way to zzzzzzz if you will).
PoC
Create two TCP in the same Namespace
Scale Kamaji to zero to avoid reconciliations
change the Kubernetes API Server
--etcd-prefixflag value to point to the other TCP datastore keywait it for get it up and running
use
kubectland will notice you're reading and writing data of another Tenant
Impact
Full control over other TCPs data, if you are able to obtain the name of other TCPs that use the same datastore and are able to obtain the user certificates used by your control plane (or you are able to configure the kube-apiserver Deployment, as shown in the PoC).
پیوندها
- https://github.com/advisories/GHSA-6r4j-4rjc-8vw5
- https://github.com/clastix/kamaji
- https://github.com/clastix/kamaji/blob/8cdc6191242f80d120c46b166e2102d27568225a/internal/datastore/etcd.go#L19-L24
- https://github.com/clastix/kamaji/commit/1731e8c2ed5148b125ecfbdf091ee177bd44f3db
- https://github.com/clastix/kamaji/security/advisories/GHSA-6r4j-4rjc-8vw5
- https://nvd.nist.gov/vuln/detail/CVE-2024-42480
گزارشدهندگان
- SimonKienzler
- prometherion

