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)
sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.
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:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
A security issue was discovered in Kubernetes where a large number of container checkpoint requests made to the unauthenticated kubelet read-only HTTP endpoint may cause a Node Denial of Service by filling the Node's disk.
Am I vulnerable?
All clusters running an affected version listed below with the kubelet read-only HTTP port enabled and using a container runtime that supports the container checkpointing feature, such as CRI-O v1.25.0+ (with enable_criu_support set to true) or containerd v2.0+ with criu installed, are affected.
Affected Versions
- kubelet v1.32.0 to v1.32.1
- kubelet v1.31.0 to v1.31.5
- kubelet v1.30.0 to v1.30.9
How do I mitigate this vulnerability?
This issue can be mitigated by setting the ContainerCheckpoint feature gate to false in your kubelet configuration, disabling the kubelet read-only port, and limiting access to the kubelet API, or upgrading to a fixed version listed below, which enforces authentication for the kubelet Checkpoint API.
Fixed Versions
- kubelet master - fixed by Kubelet server handler cleanup #129739
- kubelet v1.32.2 - fixed by Automated cherry pick of #129739: Kubelet server handler cleanup #130010
- kubelet v1.31.6 - fixed by Automated cherry pick of #129739: Kubelet server handler cleanup #130011
- kubelet v1.30.10 - fixed by Automated cherry pick of #129739: Kubelet server handler cleanup #130012
- kubelet v1.29.14 - fixed by Automated cherry pick of #129739: Kubelet server handler cleanup #130014
- Note: Container checkpoint support was an off by default Alpha feature in v1.25-v1.29
Detection
A large number of requests to the kubelet read-only HTTP server's /checkpoint endpoint, or a large number of checkpoints stored (by default) under /var/lib/kubelet/checkpoints on a Node may indicate an attempted Denial of Service attack using this bug.
If you find evidence that this vulnerability has been exploited, please contact security@kubernetes.io
Acknowledgements
This vulnerability was reported and fixed by Tim Allclair @tallclair from Google.
The issue was coordinated by:
Tim Allclair @tallclair
Sascha Grunert saschagrunert@
Craig Ingram @cji
Jordan Liggitt liggitt@
/triage accepted
/lifecycle frozen
/area security
/kind bug
/committee security-response
/label official-cve-feed
/sig node
/area kubelet
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.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.on Feb 6, 2025
- cjichanged the title ~~[-]CVE PLACEHOLDER ISSUE[/-]~~ [+]CVE-2025-0426: Node Denial of Service via kubelet Checkpoint API[/+] on Feb 13, 2025
-
dims commentedon Feb 13, 2025 MemberMore actions @cji looking at the PR in question:
kubernetes/pkg/kubelet/server/server.go
Lines 310 to 311
in
e62ce1c
if kubeCfg != nil && kubeCfg.EnableDebuggingHandlers { server.InstallDebuggingHandlers() It looks like we moved the section that registers thecheckpointurl to under the--enable-debugging-handlersas mitigation. Am i reading this right? thanks! -
tallclair commentedon Feb 13, 2025 MemberMore actions It looks like we moved the section that registers the checkpoint url to under the --enable-debugging-handlers as mitigation. Am i reading this right? thanks! Yes, correct. Except "Debugging Handlers" is misrepresentative here. Default handlers get installed on both the unauthenticated "read only" port, and the authenticated port, while "debugging handlers" are only ever installed on the authenticated port. I have a first pass at making this obvious in #129354, but we should probably also consider improving the documentation to the
EnableDebuggingHandlersoption.
Reacted by Craig Ingram, Benjamin Elder and Leo Li -
cji commentedon Feb 13, 2025 MemberAuthorMore actions /label official-cve-feed
- cjiclosed this as completedon Feb 13, 2025
- k8s-ci-robotadded 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)on Feb 13, 2025
-
cji commentedon Feb 13, 2025 MemberAuthorMore actions /sig node
/area kubelet - k8s-ci-robotadded sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.on Feb 13, 2025
-
utam0k commentedon Feb 13, 2025 MemberMore actions @cji @tallclair Thanks for your effort. I'd like to clarify the
Am I vulnerable?section. You said
with criu installed, are affected. This means If the checkpoint for runc, crun or youki fails, does this mean that this CVE is not affected?
If this is yes, I think it would be better if you explained a little more. For example, what happens with firecracker? -
dims commentedon Feb 14, 2025 MemberMore actions @tallclair thank you for the explanation!
-
khusantt commentedon Feb 14, 2025 More actions Hi everyone, For those of you who may experience a lengthy Kubelet update process, will setting the read-only port to 0 be able to protect us?
-
cji commentedon Feb 18, 2025 MemberAuthorMore actions This means If the checkpoint for runc, crun or youki fails, does this mean that this CVE is not affected? This CVE applies to clusters using any underlying CRI implementation that supports checkpointing. containerd and CRI-O were provided as non-exhaustive examples of "a container runtime that supports the container checkpointing feature". For those of you who may experience a lengthy Kubelet update process, will setting the read-only port to 0 be able to protect us? Disabling the read-only port mitigates this issue by only allowing the checkpoint API to be accessed behind authentication. Reacted by Tim Allclair
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)
sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.
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.