Repository navigation
committee/security-responseDenotes an issue or PR intended to be handled by the product security committee.Denotes an issue or PR intended to be handled by the product security committee.
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.
official-cve-feedIssues or PRs related to CVEs officially announced by Security Response Committee (SRC)Issues or PRs related to CVEs officially announced by Security Response Committee (SRC)
Description
CVSS Rating: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N - Medium (5.8)
A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This was patched for other in-tree StorageClasses (GlusterFS, Quobyte, StorageOS, and ScaleIO) as part of CVE-2020-8555. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).
An attacker with permissions to create a pod using the built-in Portworx StorageClass can cause kube-controller-manager to make GET requests (without an attacker controlled request body) from within the control plane’s host network and make the corresponding HTTP response body visible as part of event objects created by kube-controller-manager.
The in-tree Portworx StorageClass has been disabled by default starting in version v1.31 from the CSIMigrationPortworx feature gate. As a result, currently supported versions greater than or equal to v1.32 are not impacted unless the CSIMigrationPortworx feature gate is disabled with an override.
Am I vulnerable?
You may be vulnerable if all of the following are true:
- You are running a vulnerable version and have manually disabled the CSIMigrationPortworx feature gate.
- There are unprotected endpoints normally only visible from the control plane’s host network (including link-local metadata endpoints, unauthenticated services listening on localhost, or other services in the control plane’s private network).
- Untrusted users can create pods with the affected Portworx volume type.
Affected Versions
The CSIMigrationPortworx feature gate was enabled by default starting on version v1.31. As a result, EOL versions \<= v1.30 are more likely to be vulnerable because the CSIMigrationPortworx feature is disabled by default.
- kube-controller-manager: \<= v1.30.14
- kube-controller-manager: \<= v1.31.14
- kube-controller-manager: \<= v1.32.9
- kube-controller-manager: \<= v1.33.5
- kube-controller-manager: \<= v1.34.1
How do I mitigate this vulnerability?
This issue can be mitigated by upgrading to a fixed kube-controller-manager version or by enabling the CSIMigrationPortworx feature gate (if it was overridden from its default value in versions greater than equal to v1.31).
Fixed Versions
- kube-controller-manager: >= v1.32.10
- kube-controller-manager: >= v1.33.6
- kube-controller-manager: >= v1.34.2
Detection
This issue can be detected on clusters which have the CSIMigrationPortworx feature gate disabled on impacted versions by analyzing ProvisioningFailed events from kube-controller-manager which may contain sensitive information from the control plane’s host network.
If you find evidence that this vulnerability has been exploited, please contact security@kubernetes.io
Acknowledgements
This vulnerability was reported by:
- Xingyu Liu (xingyu@stu.xidian.edu.cn)
- Jinku Li (jkli@xidian.edu.cn)
The issue was fixed and coordinated by:
- Ankit Gohil @gohilankit
Activity
- k8s-ci-robotadded needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.Indicates an issue or PR lacks a `sig/foo` label and requires one.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.on Nov 30, 2025
-
k8s-ci-robot commentedon Nov 30, 2025 ContributorMore actions This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the
triage/acceptedlabel and provide further guidance.
Thetriage/acceptedlabel can be added by org members by writing/triage acceptedin a comment.
Details Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
- natherz97changed the title ~~[-]CVE-2025-13281: \[/-]~~ [+]CVE-2025-13281: Portworx Half-Blind SSRF in kube-controller-manager[/+] on Dec 1, 2025
-
natherz97 commentedon Dec 1, 2025 AuthorMore actions /area security
/kind bug
/committee security-response
/label official-cve-feed - k8s-ci-robotadded kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.committee/security-responseDenotes an issue or PR intended to be handled by the product security committee.Denotes an issue or PR intended to be handled by the product security committee.official-cve-feedIssues or PRs related to CVEs officially announced by Security Response Committee (SRC)Issues or PRs related to CVEs officially announced by Security Response Committee (SRC) and removed needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.Indicates an issue or PR lacks a `sig/foo` label and requires one.on Dec 1, 2025
-
natherz97 commentedon Dec 1, 2025 AuthorMore actions Fixed by:
- kube-controller-manager: master - Clean up event messages for errors in Portworx in-tree driver #135081
- kube-controller-manager: v1.32.10 - Automated cherry pick of #135081: Clean up event messages for errors in Portworx in-tree driver #135193
- kube-controller-manager: v1.33.6 - Automated cherry pick of #135081: Clean up event messages for errors in Portworx in-tree driver #135192
- kube-controller-manager: v1.34.2 - Automated cherry pick of #135081: Clean up event messages for errors in Portworx in-tree driver #135191
- natherz97closed this as completedon Dec 3, 2025
Metadata
Metadata
Assignees
Labels
committee/security-responseDenotes an issue or PR intended to be handled by the product security committee.Denotes an issue or PR intended to be handled by the product security committee.
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.
official-cve-feedIssues or PRs related to CVEs officially announced by Security Response Committee (SRC)Issues or PRs related to CVEs officially announced by Security Response Committee (SRC)