Skip to content

Kubernetes csi-proxy vulnerable to privilege escalation due to improper input validation

High severity GitHub Reviewed Published Nov 3, 2023 to the GitHub Advisory Database • Updated Jul 9, 2025

Package

gomod github.com/kubernetes-csi/csi-proxy (Go)

Affected versions

>= 0.1.0-rc1, <= 1.1.2
< 0.0.0-20230821192013-2523e6674ded
>= 1.1.3-0, < 1.1.3-0.20230821192013-2523e6674ded

Patched versions

1.1.3
0.0.0-20230821192013-2523e6674ded
1.1.3-0.20230821192013-2523e6674ded
gomod github.com/kubernetes-csi/csi-proxy/v2 (Go)
= 2.0.0-alpha.0
2.0.0-alpha.1

Description

Kubernetes is vulnerable to privilege escalation when 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.

References

Published by the National Vulnerability Database Nov 3, 2023
Published to the GitHub Advisory Database Nov 3, 2023
Reviewed Nov 3, 2023
Last updated Jul 9, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(87th percentile)

Weaknesses

Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Learn more on MITRE.

CVE ID

CVE-2023-3893

GHSA ID

GHSA-r6cc-7wj7-gfx2

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.