CVE-2023-3893GO-2023-2176GHSA-R6CC-7WJ7-GFX2
Kubernetes - csi-proxy - Insufficient input sanitization leads to privilege escalation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.1.3, 2.0.0-alpha.1, 0.0.0-20230821192013-2523e6674ded, 1.1.3-0.20230821192013-2523e6674ded
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Kubernetes csi-proxy
through v1.1.2
- github.com/kubernetes-csi/csi-proxyGo
fixed in 1.1.3
- github.com/kubernetes-csi/csi-proxy/v2Go
From 2.0.0-alpha.0 · fixed in 2.0.0-alpha.1
- github.com/kubernetes-csi/csi-proxy/v2Go
From 2.0.0-alpha.0 · fixed in 2.0.0-alpha.1
- github.com/kubernetes-csi/csi-proxyGo
From 0.1.0-rc1 · fixed in 1.1.3
- github.com/kubernetes-csi/csi-proxyGo
fixed in 0.0.0-20230821192013-2523e6674ded
- github.com/kubernetes-csi/csi-proxyGo
From 1.1.3-0 · fixed in 1.1.3-0.20230821192013-2523e6674ded