dbcve.org
Flux2Application · Fluxcd

CVE-2022-24877

HIGH · 8.8 CVSS v3.1 Published 2022-05-06
Fix available
A fix is available. Upgrade to 0.24.0 / 0.29.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Flux is an open and extensible continuous delivery solution for Kubernetes. Path Traversal in the kustomize-controller via a malicious `kustomization.yaml` allows an attacker to expose sensitive data from the controller’s pod filesystem and possibly privilege escalation in multi-tenancy deployments. Workarounds include automated tooling in the user's CI/CD pipeline to validate `kustomization.yaml` files conform with specific policies. This vulnerability is fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0.

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

A path traversal vulnerability in the kustomize-controller component of Flux allows attackers to craft malicious kustomization.yaml files that access files outside the intended kustomization build context. This enables exposure of sensitive data from the controller's pod filesystem and potential privilege escalation in multi-tenant Kubernetes environments.

MitigationUpgrade kustomize-controller to v0.24.0 or later (flux2 v0.29.0+). Alternatively, implement CI/CD pipeline validation to detect and reject non-compliant kustomization.yaml files before deployment.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Flux2Application
Affected:< 0.29.0
Kustomize ControllerApplication
Affected:< 0.24.0

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
High

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

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 kustomize-controller version
    Run 'kubectl get deployment -A -l app=kustomize-controller -o jsonpath="{.items[*].spec.template.spec.containers[0].image}"' to get the container image, or check the image of the kustomize-controller pod
    Affected if The version is below 0.24.0 (check image tag for kustomize-controller like v0.23.0 or earlier)
  2. Identify Flux2 version
    Run 'flux version' on the cluster controller pod or check the flux-system namespace for the controllers' image tags
    Affected if The Flux2 version is below 0.29.0 (check all flux controller images for versions like v0.28.0 or earlier)
  3. Verify kustomization CRDs exist
    Run 'kubectl get crd -A | grep -E "(kustomization|ksets)"' to confirm kustomize-controller is actively managing resources
    Affected if Kustomization or KustomSet CRDs are present, meaning kustomize-controller is deployed and processing custom resources
  4. Inspect kustomization.yaml files in clusters
    Review all kustomization.yaml files in your Git repositories for path traversal patterns like '../' or absolute paths pointing outside the build context, or run 'kubectl get Kustomization -A -o yaml' to see active configurations
    Affected if Any kustomization.yaml contains '..' path references or references files from parent directories outside the expected build context

You are affected if kustomize-controller is below v0.24.0 (or Flux2 below v0.29.0) AND you have kustomization resources that could process malicious kustomization.yaml files with path traversal patterns.

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
Upgrade available Upgrade to 0.24.0 / 0.29.0 or later
Fixed in 0.24.00.29.0
Interim mitigation

Upgrade kustomize-controller to v0.24.0 or later (flux2 v0.29.0+). Alternatively, implement CI/CD pipeline validation to detect and reject non-compliant kustomization.yaml files before deployment.

Recommended fix High confidence

kustomize-controller v0.24.0 or flux2 v0.29.0

  1. Check current version of kustomize-controller or flux2 in your cluster: kubectl get deploy -n flux-system kustomize-controller -o jsonpath='{.spec.template.spec.containers[0].image}'
  2. Upgrade kustomize-controller to v0.24.0 or later using your deployment method (Helm upgrade, kubectl apply, flux bootstrap, etc.)
  3. Alternatively, upgrade flux2 to v0.29.0 or later which includes the fixed kustomize-controller
  4. Verify the upgrade was successful: kubectl get deploy -n flux-system kustomize-controller -o jsonpath='{.spec.template.spec.containers[0].image}' | grep -E '(v0\.2[4-9]|[0-9]+\.[3-9][0-9]+\.)'
  5. Ensure your CI/CD pipeline validates kustomization.yaml files if immediate upgrade is not possible

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

Fix this in Flux2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24877 — 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-2022-24877 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