# CVE-2022-3162: Unauthorized read of Custom Resources > Users with cluster-wide list permissions on one custom resource can read unauthorized custom resources in the same API group. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Mar 2023 - **Updated:** 7 Mar 2025 - **Also known as:** AZL-13780, AZL-13781, AZL-13782, AZL-13783, AZL-25938, AZL-31287, AZL-34838, DEBIAN-CVE-2022-3162, GHSA-2394-5535-8j88, GO-2023-1628, RHSA-2023:0772 ## What is CVE-2022-3162? CVE-2022-3162 is a medium-severity missing authorization vulnerability in Kubernetes Kubernetes, published on 1 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-23 (Relative Path Traversal) ## Which versions are affected by CVE-2022-3162? 9 open source packages ship an affected version, including github.com/kubernetes/kubernetes and k8s.io/kubernetes. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/kubernetes/kubernetes` | Go | From 1.22.0 | 1.22.16 | | `github.com/kubernetes/kubernetes` | Go | From 1.22.0 | 1.22.16 | | `github.com/kubernetes/kubernetes` | Go | From 1.23.0 | 1.23.14 | | `github.com/kubernetes/kubernetes` | Go | From 1.23.0 | 1.23.14 | | `github.com/kubernetes/kubernetes` | Go | From 1.24.0 | 1.24.8 | | `github.com/kubernetes/kubernetes` | Go | From 1.24.0 | 1.24.8 | | `github.com/kubernetes/kubernetes` | Go | From 1.25.0 | 1.25.4 | | `github.com/kubernetes/kubernetes` | Go | From 1.25.0 | 1.25.4 | | `k8s.io/kubernetes` | Go | From 1.22.0 | 1.22.16, 1.23.14, 1.24.8, 1.25.4 | | `microshift` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.4-202302151633.p0.gb9fe8ac.assembly.4.12.4.el8 | | `microshift-networking` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.4-202302151633.p0.gb9fe8ac.assembly.4.12.4.el8 | | `microshift-release-info` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.4-202302151633.p0.gb9fe8ac.assembly.4.12.4.el8 | | `microshift-selinux` | Red Hat:openshift:4.12::el8 | All versions | 0:4.12.4-202302151633.p0.gb9fe8ac.assembly.4.12.4.el8 | Products: Kubernetes Kubernetes. ## How do I fix CVE-2022-3162? Upgrade github.com/kubernetes/kubernetes to a fixed version for your release line: 1.22.16, 1.23.14, 1.24.8 or 1.25.4. ## Is CVE-2022-3162 being exploited? There is no known exploitation of CVE-2022-3162 in the wild and no public exploit code. ## Other vulnerabilities in Kubernetes Kubernetes - [CVE-2018-1002105](https://insights.sbomify.com/CVE-2018-1002105/): Privilege Escalation in Kubernetes (critical 9.8) - [CVE-2017-1000056](https://insights.sbomify.com/CVE-2017-1000056/): Kubernetes Privilege Escalation (critical 9.8) - [CVE-2016-1906](https://insights.sbomify.com/CVE-2016-1906/): Authorization bypass in Openshift (critical 9.8) - [CVE-2023-3676](https://insights.sbomify.com/CVE-2023-3676/): Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation (high 8.8) - [CVE-2023-3955](https://insights.sbomify.com/CVE-2023-3955/): Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-3162 and fix it if it is affected. What it is: CVE-2022-3162 is a medium-severity missing authorization vulnerability in Kubernetes Kubernetes, published on 1 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-3162 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/kubernetes/kubernetes (Go): affected from 1.22.0; fixed in 1.22.16 - github.com/kubernetes/kubernetes (Go): affected from 1.22.0; fixed in 1.22.16 - github.com/kubernetes/kubernetes (Go): affected from 1.23.0; fixed in 1.23.14 - github.com/kubernetes/kubernetes (Go): affected from 1.23.0; fixed in 1.23.14 - github.com/kubernetes/kubernetes (Go): affected from 1.24.0; fixed in 1.24.8 - github.com/kubernetes/kubernetes (Go): affected from 1.24.0; fixed in 1.24.8 - github.com/kubernetes/kubernetes (Go): affected from 1.25.0; fixed in 1.25.4 - github.com/kubernetes/kubernetes (Go): affected from 1.25.0; fixed in 1.25.4 - k8s.io/kubernetes (Go): affected from 1.22.0; fixed in 1.22.16, 1.23.14, 1.24.8, 1.25.4 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-3162/ (Markdown: https://insights.sbomify.com/CVE-2022-3162/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3162 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3162 - OSV: https://osv.dev/vulnerability/CVE-2022-3162 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-3162/ Summaries are generated and may contain mistakes; the official description above is the record.