Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2022-3162: Unauthorized read of Custom Resources #177

Open
pacoxu opened this issue Nov 11, 2022 · 1 comment
Open

CVE-2022-3162: Unauthorized read of Custom Resources #177

pacoxu opened this issue Nov 11, 2022 · 1 comment

Comments

@pacoxu
Copy link
Member

pacoxu commented Nov 11, 2022

What happened?

kubernetes/kubernetes#113756

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

@github-actions
Copy link

Hi @pacoxu,
Thanks for opening an issue!
We will look into it as soon as possible.

Details Instructions for interacting with me using comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the [gh-ci-bot](https://github.com/wzshiming/gh-ci-bot) repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant