dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-10220

HIGH · 8.1 CVSS v3.1 Published 2024-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Kubernetes kubelet component allows arbitrary command execution via specially crafted gitRepo volumes.This issue affects kubelet: through 1.28.11, from 1.29.0 through 1.29.6, from 1.30.0 through 1.30.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Kubernetes kubelet contains a command injection vulnerability in its gitRepo volume handling. Attackers who can create or modify pods with gitRepo volumes can execute arbitrary commands on the node where the kubelet processes them, potentially leading to container escape and node compromise.

MitigationUpgrade kubelet to version 1.28.12, 1.29.7, 1.30.3, or later. If immediate patching is not possible, disable gitRepo volume support in kubelet via the --enable-server=false flag or use admission controls to reject pods using gitRepo volumes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify kubelet version
    Run `kubelet --version` on each node or check via `kubectl get nodes -o wide` to see kubelet version information
    Affected if kubelet version is 1.28.x before 1.28.12, 1.29.x before 1.29.7, or 1.30.x before 1.30.3
  2. Identify gitRepo volume usage in the cluster
    Run `kubectl get pods --all-namespaces -o jsonpath='{range .items[*]}{.metadata.namespace}{.metadata.name}{.spec.volumes[*].gitRepo}{"\n"}{end}'` to list all pods using gitRepo volumes
    Affected if Any pods exist in the cluster that use gitRepo volumes in their spec
  3. Check for pod creation or modification permissions
    Review RBAC policies using `kubectl auth can-i create pods` or `kubectl auth can-i edit pods` from untrusted service accounts or namespaces
    Affected if Untrusted users or service accounts have permission to create or modify pods with arbitrary specifications
  4. Verify node accessibility
    Ensure that only trusted container images and volume specifications are allowed in pods running on sensitive nodes
    Affected if Untrusted pods with gitRepo volumes can be scheduled onto nodes running vulnerable kubelet versions

You are affected if your kubelet version falls within the vulnerable range AND gitRepo volumes are being used in your cluster AND untrusted users can create or modify pods.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade kubelet to version 1.28.12, 1.29.7, 1.30.3, or later. If immediate patching is not possible, disable gitRepo volume support in kubelet via the --enable-server=false flag or use admission controls to reject pods using gitRepo volumes.

Recommended fix High confidence

kubelet 1.28.12, 1.29.7, or 1.30.3 (and later patch versions within each minor release)

  1. Identify the current kubelet version in your Kubernetes cluster using 'kubelet --version' or checking the node's kubelet process
  2. Plan a maintenance window for the upgrade, ensuring proper node cordoning/draining procedures
  3. Upgrade kubelet to version 1.28.12 or later for Kubernetes 1.28 clusters, OR
  4. Upgrade kubelet to version 1.29.7 or later for Kubernetes 1.29 clusters, OR
  5. Upgrade kubelet to version 1.30.3 or later for Kubernetes 1.30 clusters
  6. After upgrade, verify kubelet is running the patched version and test that gitRepo volume functionality works as expected
  7. For production clusters, upgrade control plane nodes first, then worker nodes, following standard Kubernetes upgrade procedures
Caveat Patch upgrades typically have minimal breaking changes; however, review Kubernetes release notes for any known issues before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10220 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10220 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data