Repository navigation
kubermatic/kubermatic#14783kubermatic/kubermatic#14783
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.
lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.
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)
triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Description
CVSS Rating:
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L - Low (2.7)
A vulnerability exists in the NodeRestriction admission controller where nodes can bypass dynamic resource allocation authorization checks. When the DynamicResourceAllocation feature gate is enabled, the controller properly validates resource claim statuses during pod status updates but fails to perform equivalent validation during pod creation. This allows a compromised node to create mirror pods that access unauthorized dynamic resources, potentially leading to privilege escalation. In practice, sanity checks in the kubelet prevent starting those mirror pods after they have been created. Even if they were started, an attacker probably already has gained full access to the node and with most dynamic resources won’t be able to gain additional privileges.
Am I vulnerable?
All clusters that are using the DynamicResourceAllocation feature (disabled by default) and static pods together may be vulnerable.
Affected Versions
kube-apiserver: v1.32.0 - v1.32.5
kube-apiserver: v1.33.0 - 1.33.1
How do I mitigate this vulnerability?
This issue can be mitigated by:
If you're not actively using the DynamicResourceAllocation features, the safest and simplest action is to turn off the feature on the API server.
Fixed Versions
kube-apiserver >= v1.32.6
kube-apiserver >= v1.33.2
Detection
All clusters that are using the DynamicResourceAllocation feature and static pods may be vulnerable. Run the following command to see if the feature is in use:
kubectl get ResourceClaim --all-namespaces
and
kubectl get pods --all-namespaces -o json | jq -r ' .items[] | select(.metadata.annotations["kubernetes.io/config.mirror"] == "true") | "\(.metadata.namespace)/\(.metadata.name)"'
If you find evidence that this vulnerability has been exploited, please contact security@kubernetes.io
Acknowledgements
This vulnerability was reported by Amit Schendel @amitschendel ARMO
The issue was fixed and coordinated by:
Patrick Ohly @pohly
Jordan Liggitt @liggitt
Balaji @SaranBalaji90
Rita Zhang @ritazh
Marko Mudrinić @xmudrii
/triage accepted
/lifecycle frozen
Activity
- k8s-ci-robotadded lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.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 Jun 6, 2025
- ritazhchanged the title ~~[-][placeholder] for release[/-]~~ [+]CVE-2025-4563: Nodes can bypass dynamic resource allocation authorization checks[/+] on Jun 18, 2025
-
ritazh commentedon Jun 18, 2025 MemberAuthorMore 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 Jun 18, 2025
-
ritazh commentedon Jun 18, 2025 MemberAuthorMore actions
- ritazhclosed this as completedon Jun 18, 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.
lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.
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)
triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.