Unauthorized read of Custom Resources
Kubernetes
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kubernetes/kubernetes Go |
|
|
Kubernetes
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kubernetes/kubernetes Go |
|
|
| k8s.io/kubernetes Go |
|
|
Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom resources of a different type in the same API group without authorization. Clusters are impacted by this vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The same users are not authorized to read another custom resource in the same API group.
From the CVE record · kubernetes
Kubernetes can allow users with cluster-wide list or watch permission on one namespaced custom resource to read a different custom resource in the same API group without authorization. This affects clusters with at least two CustomResourceDefinitions in that group when those users lack permission to read the other resource; the attacker must have the specified authorization.
Operators running Kubernetes or the Go packages github.com/kubernetes/kubernetes or k8s.io/kubernetes at versions 1.22.0–1.22.15, 1.23.0–1.23.13, 1.24.0–1.24.7, or 1.25.0–1.25.3 should check their clusters.