dbcve.org
Flux2Application · Fluxcd

CVE-2022-24878

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
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 cause a Denial of Service at the controller level. 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. Users are recommended to upgrade.

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 · moderate confidence

Path traversal vulnerability in kustomize-controller allows attackers to craft malicious kustomization.yaml files that can cause a Denial of Service at the controller level in Flux CD deployments for Kubernetes.

MitigationUpgrade to kustomize-controller v0.24.0 or flux2 v0.29.0; alternatively, implement CI/CD pipeline validation tooling to enforce policies on 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 deployment version
    Run: kubectl get deployment -A -o jsonpath='{..metadata.name}' | tr ' ' '\n' | grep kustomize-controller. Then get the image with: kubectl get deployment -n flux-system kustomize-controller -o jsonpath='{.spec.template.spec.containers[0].image}'
    Affected if The image tag shows a version lower than v0.24.0 (e.g., v0.23.0, v0.22.0, etc.)
  2. Identify flux2 CLI version
    Run: flux --version
    Affected if The reported flux version is lower than 0.29.0 (e.g., 0.28.0, 0.27.0, etc.)
  3. Verify kustomize-controller is running
    Run: kubectl get pods -n flux-system -l app=kustomize-controller
    Affected if The controller pod exists and is in Running status, indicating it can process kustomization.yaml files
  4. Check if any kustomization resources exist
    Run: kubectl get kustomization -A
    Affected if Any Kustomization resources are present in the cluster, meaning the controller would process kustomization.yaml files containing the vulnerable code path
  5. Confirm namespace where flux is installed
    Run: kubectl get namespaces | grep -E 'flux|weave-gitops'
    Affected if The flux-system namespace (or custom flux namespace) exists with the controller deployed

You are affected if the kustomize-controller image version is below v0.24.0 OR the flux CLI version is below 0.29.0, and the controller is actively running in your cluster to process kustomization resources.

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 to kustomize-controller v0.24.0 or flux2 v0.29.0; alternatively, implement CI/CD pipeline validation tooling to enforce policies on kustomization.yaml files before deployment.

Recommended fix High confidence

flux2 v0.29.0 or kustomize-controller v0.24.0

  1. Check current Flux2 or kustomize-controller version using: flux version or kubectl -n flux-system get pods -o jsonpath='{.items[*].spec.containers[*].image}'
  2. If running Flux2, upgrade to version 0.29.0 or later by updating your Flux installation: flux install --version=0.29.0
  3. If running kustomize-controller separately, upgrade to version 0.24.0 or later
  4. Verify the upgrade was successful by checking the controller version and ensuring all pods are running: flux check --pre and kubectl get pods -n flux-system
  5. Alternatively, if using GitOps, update your Flux bootstrap to the new version and apply the changes

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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