# CVE-2022-3294: Node address isn't always verified when proxying > Authenticated users can bypass node proxy validation to access private network endpoints in the Kubernetes control plane. - **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Mar 2023 - **Updated:** 7 Mar 2025 - **Also known as:** DEBIAN-CVE-2022-3294, GHSA-jh36-q97c-9928, GO-2023-1629, RHBA-2023:0452, openSUSE-SU-2024:12737-1 ## What is CVE-2022-3294? CVE-2022-3294 is a medium-severity server-side request forgery vulnerability in Kubernetes Kubernetes, published on 1 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports node proxying, which allows clients of kube-apiserver to access endpoints of a Kubelet to establish connections to Pods, retrieve container logs, and more. While Kubernetes already validates the proxying address for Nodes, a bug in kube-apiserver made it possible to bypass this validation. Bypassing this validation could allow authenticated requests destined for Nodes to to the API server's private network. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2022-3294? 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.1-202301261525.p0.g3db9e81.assembly.4.12.1.el8 | Products: Kubernetes Kubernetes. ## How do I fix CVE-2022-3294? 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-3294 being exploited? There is no known exploitation of CVE-2022-3294 in the wild and no public exploit code. Public exploit code: - Privilege Escalation using nodes/proxy (create action allowed) and nodes/status (update/patch actions allowed) (github_poc): https://github.com/arbaaz29/CVE-2022-3294 ## 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-3294 and fix it if it is affected. What it is: CVE-2022-3294 is a medium-severity server-side request forgery vulnerability in Kubernetes Kubernetes, published on 1 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-3294 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-3294/ (Markdown: https://insights.sbomify.com/CVE-2022-3294/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3294 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3294 - OSV: https://osv.dev/vulnerability/CVE-2022-3294 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-3294/ Summaries are generated and may contain mistakes; the official description above is the record.