dbcve.org
Flux2Application · Fluxcd

CVE-2022-36035

HIGH · 7.8 CVSS v3.1 Published 2022-08-31
Fix available
A fix is available. Upgrade to 0.32.0 or later.
See remediation →
80/100
Remediation priority · High
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 a tool for keeping Kubernetes clusters in sync with sources of configuration (like Git repositories), and automating updates to configuration when there is new code to deploy. Flux CLI allows users to deploy Flux components into a Kubernetes cluster via command-line. The vulnerability allows other applications to replace the Flux deployment information with arbitrary content which is deployed into the target Kubernetes cluster instead. The vulnerability is due to the improper handling of user-supplied input, which results in a path traversal that can be controlled by the attacker. Users sharing the same shell between other applications and the Flux CLI commands could be affected by this vulnerability. In some scenarios no errors may be presented, which may cause end users not to realize that something is amiss. A safe workaround is to execute Flux CLI in ephemeral and isolated shell environments, which can ensure no persistent values exist from previous processes. However, upgrading to the latest version of the CLI is still the recommended mitigation strategy.

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 Flux CLI vulnerability allows path traversal through improper handling of user-supplied input, enabling other applications sharing the same shell environment to inject arbitrary content into Kubernetes cluster deployments instead of the intended Flux configuration.

MitigationUpgrade to the latest Flux CLI version. As a workaround, execute Flux CLI commands in ephemeral and isolated shell environments to prevent injection from persistent process values.

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.21.0, < 0.32.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Verify Flux CLI is installed
    Run 'flux --version' or 'flux version' to confirm Flux CLI is present in your environment
    Affected if Flux CLI is not installed, this CVE does not apply
  2. Identify the installed Flux CLI version
    Execute 'flux --version' and note the version number displayed
    Affected if The version falls within >= 0.21.0 and < 0.32.0, indicating the environment is potentially affected
  3. Confirm Flux is managing Kubernetes resources
    Run 'flux get all --all-namespaces' or check if Flux controllers are deployed in any cluster namespace using 'kubectl get pods -A | grep flux'
    Affected if Flux is actively managing Kubernetes resources and the version is affected, the path traversal could allow injection into cluster deployments
  4. Check shell environment persistence
    Review whether Flux commands are run in persistent shell sessions, container shells, or shared terminal multiplexers rather than isolated ephemeral environments
    Affected if Flux shares its shell environment with other processes, the vulnerability could allow those processes to inject content through environment variables or shell state

You are affected if Flux CLI version is 0.21.0 through 0.31.x inclusive AND Flux is actively managing Kubernetes resources in an environment with shared shell access.

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.32.0 or later
Fixed in 0.32.0
Interim mitigation

Upgrade to the latest Flux CLI version. As a workaround, execute Flux CLI commands in ephemeral and isolated shell environments to prevent injection from persistent process values.

Recommended fix High confidence

Flux2 CLI version 0.32.0 or later

  1. Verify current Flux CLI version by running: flux --version
  2. Download and install Flux CLI version 0.32.0 or later using the official install script: curl -s https://fluxcd.io/install.sh | bash
  3. Alternatively, if using Homebrew, upgrade Flux: brew upgrade fluxcd/flux/flux
  4. Verify the new version is installed: flux --version
  5. Ensure the Flux CLI components are updated in any existing deployments by re-running flux install or flux bootstrap as needed

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

Fix this in Flux2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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