-
Notifications
You must be signed in to change notification settings - Fork 16
Description
What happened?
A security issue was discovered in Kubernetes where 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.
This issue has been rated Medium (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), and assigned CVE-2022-3162
What did you expect to happen?
Clusters are impacted by this vulnerability if all of the following are true:
There are 2+ CustomResourceDefinitions sharing the same API group
Users have cluster-wide list or watch authorization on one of those custom resources.
The same users are not authorized to read another custom resource in the same API group.
How can we reproduce it (as minimally and precisely as possible)?
Affected Versions
• Kubernetes kube-apiserver <= v1.25.3
• Kubernetes kube-apiserver <= v1.24.7
• Kubernetes kube-apiserver <= v1.23.13
• Kubernetes kube-apiserver <= v1.22.15
Anything else we need to know?
No response