# CVE-2023-3893: Kubernetes - csi-proxy - Insufficient input sanitization leads to privilege escalation > A user creating pods on Windows nodes can escalate to admin privileges due to insufficient input sanitization in csi-proxy. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **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:** 3 Nov 2023 - **Updated:** 13 Feb 2025 - **Also known as:** DEBIAN-CVE-2023-3893, GHSA-r6cc-7wj7-gfx2, GO-2023-2176 ## What is CVE-2023-3893? CVE-2023-3893 is a high-severity vulnerability in Kubernetes csi-proxy, published on 3 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes running kubernetes-csi-proxy may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Windows nodes running kubernetes-csi-proxy. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2023-3893? 10 open source packages ship an affected version, including github.com/kubernetes-csi/csi-proxy and github.com/kubernetes-csi/csi-proxy/v2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/kubernetes-csi/csi-proxy` | Go | All versions | 0.0.0-20230821192013-2523e6674ded | | `github.com/kubernetes-csi/csi-proxy` | Go | All versions | 0.0.0-20230821192013-2523e6674ded | | `github.com/kubernetes-csi/csi-proxy` | Go | All versions | 1.1.3 | | `github.com/kubernetes-csi/csi-proxy` | Go | From 0.1.0-rc1 | 1.1.3 | | `github.com/kubernetes-csi/csi-proxy` | Go | From 0.1.0-rc1 | 1.1.3 | | `github.com/kubernetes-csi/csi-proxy` | Go | From 1.1.3-0 | 1.1.3-0.20230821192013-2523e6674ded | | `github.com/kubernetes-csi/csi-proxy` | Go | From 1.1.3-0 | 1.1.3-0.20230821192013-2523e6674ded | | `github.com/kubernetes-csi/csi-proxy/v2` | Go | From 2.0.0-alpha.0 | 2.0.0-alpha.1 | | `github.com/kubernetes-csi/csi-proxy/v2` | Go | From 2.0.0-alpha.0 | 2.0.0-alpha.1 | | `github.com/kubernetes-csi/csi-proxy/v2` | Go | From 2.0.0-alpha.0 | 2.0.0-alpha.1 | Products: Kubernetes Csi Proxy. ## How do I fix CVE-2023-3893? Upgrade github.com/kubernetes-csi/csi-proxy to a fixed version for your release line: 0.0.0-20230821192013-2523e6674ded, 1.1.3 or 1.1.3-0.20230821192013-2523e6674ded. ## Is CVE-2023-3893 being exploited? There is no known exploitation of CVE-2023-3893 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-3893 and fix it if it is affected. What it is: CVE-2023-3893 is a high-severity vulnerability in Kubernetes csi-proxy, published on 3 Nov 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-2023-3893 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/kubernetes-csi/csi-proxy (Go): affected all versions; fixed in 0.0.0-20230821192013-2523e6674ded - github.com/kubernetes-csi/csi-proxy (Go): affected all versions; fixed in 0.0.0-20230821192013-2523e6674ded - github.com/kubernetes-csi/csi-proxy (Go): affected all versions; fixed in 1.1.3 - github.com/kubernetes-csi/csi-proxy (Go): affected from 0.1.0-rc1; fixed in 1.1.3 - github.com/kubernetes-csi/csi-proxy (Go): affected from 0.1.0-rc1; fixed in 1.1.3 - github.com/kubernetes-csi/csi-proxy (Go): affected from 1.1.3-0; fixed in 1.1.3-0.20230821192013-2523e6674ded - github.com/kubernetes-csi/csi-proxy (Go): affected from 1.1.3-0; fixed in 1.1.3-0.20230821192013-2523e6674ded - github.com/kubernetes-csi/csi-proxy/v2 (Go): affected from 2.0.0-alpha.0; fixed in 2.0.0-alpha.1 - github.com/kubernetes-csi/csi-proxy/v2 (Go): affected from 2.0.0-alpha.0; fixed in 2.0.0-alpha.1 - github.com/kubernetes-csi/csi-proxy/v2 (Go): affected from 2.0.0-alpha.0; fixed in 2.0.0-alpha.1 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-2023-3893/ (Markdown: https://insights.sbomify.com/CVE-2023-3893/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-3893 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-3893 - OSV: https://osv.dev/vulnerability/CVE-2023-3893 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-3893/ Summaries are generated and may contain mistakes; the official description above is the record.