CVE-2022-24817: Github.com/fluxcd/flux2 Improper Kubeconfig Validation Allows Arbitrary Vulnerability

CRITICAL
Advisory Identifier: GHSA-vvmq-fwmg-2gjc
CVSS 9.9
CWE-94
Published
Advisory Summary

CVE-2022-24817 is a CRITICAL (CVSS 9.9) improper kubeconfig validation allows arbitrary vulnerability (CWE-94: Improper Control of Generation of Code ('Code Injection')) affecting Github.com/fluxcd/flux2 libraries in the Go ecosystem. The issue involves improper kubeconfig validation allows arbitrary code execution. Remediation is available by upgrading affected packages to version 0.29.0, 0.23.0, 0.19.0.

CVE-2022-24817 at a Glance

CVE Identifier CVE-2022-24817
GHSA Identifier GHSA-vvmq-fwmg-2gjc
Severity CRITICAL
CVSS v3.1 Base Score 9.9
CWE Classification CWE-94: Improper Control of Generation of Code ('Code Injection')
Affected Product Github.com/fluxcd/flux2
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 9.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2022-24817

To remediate this vulnerability, upgrade all affected Github.com/fluxcd/flux2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/fluxcd/flux2 fixed: 0.29.0
Upgrade github.com/fluxcd/flux2 to 0.29.0
github.com/fluxcd/kustomize-controller fixed: 0.23.0
Upgrade github.com/fluxcd/kustomize-controller to 0.23.0
github.com/fluxcd/helm-controller fixed: 0.19.0
Upgrade github.com/fluxcd/helm-controller to 0.19.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/fluxcd/flux2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2022-24817, inspect your project dependencies for Github.com/fluxcd/flux2:

inspect dependencies for github.com/fluxcd/flux2

Analyze the terminal output to locate any version of Github.com/fluxcd/flux2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.29.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-94: Improper Control of Generation of Code ('Code Injection'), where the product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. In Github.com/fluxcd/flux2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Flux2 can reconcile the state of a remote cluster when provided with a [kubeconfig](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/#file-references) with the correct access rights. `Kubeconfig` files can define [commands](https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins) to be executed to generate on-demand authentication tokens. A malicious user with write access to a Flux source or direct access to the target cluster, could craft a `kubeconfig` to execute arbitrary code inside the controller’s container. In multi-tenancy deployments this can also lead to privilege escalation if the controller's service account has elevated permissions. ### Impact Within the affected versions range, one of the permissions set below would be required for the vulnerability to be exploited: - Direct access to the cluster to create Flux `Kustomization` or `HelmRelease` objects and Kubernetes Secrets. - Direct access to the cluster to modify existing Kubernetes secrets being used as `kubeconfig` in existing Flux `Kustomization` or `HelmRelease` objects. - Direct access to the cluster to modify existing Flux `Kustomization` or `HelmRelease` objects and access to create or modify existing Kubernetes secrets. - Access rights to make changes to a configured Flux Source (i.e. Git repository). ### Patches This vulnerability was fixed in kustomize-controller [v0.23.0](https://github.com/fluxcd/kustomize-controller/releases/tag/v0.23.0) and helm-controller [v0.19.0](https://github.com/fluxcd/helm-controller/releases/tag/v0.19.0), both included in flux2 [v0.29.0](https://github.com/fluxcd/flux2/releases/tag/v0.29.0). Starting from the fixed versions, both controllers disable the use of command execution from `kubeconfig` files by default, users have to opt-in by adding the flag `--insecure-kubeconfig-exec` to the controller’s command arguments. Users are no longer allowed to refer to files in the controller’s filesystem in the `kubeconfig` files provided for the remote apply feature. ### Workarounds - The functionality can be disabled via Validating Admission webhooks (e.g. OPA Gatekeeper, Kyverno) by restricting users from being able to set the `spec.kubeConfig` field in Flux `Kustomization` and `HelmRelease` objects. - Applying restrictive AppArmor and SELinux profiles on the controller’s pod to limit what binaries can be executed. ### Credits The Flux engineering team found and patched this vulnerability. ### For more information If you have any questions or comments about this advisory please open an issue in the [flux2 repository](http://github.com/fluxcd/flux2).

CVE-2022-24817 Affected Github.com/fluxcd/flux2 Versions

3 component(s)
Fixed Versions:
0.29.00.23.00.19.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/fluxcd/flux2
Go
≥ 0.1.0
< 0.29.0
0.29.0
github.com/fluxcd/kustomize-controller
Go
≥ 0.1.0
< 0.23.0
0.23.0
github.com/fluxcd/helm-controller
Go
≥ 0.2.0
< 0.19.0
0.19.0

References

Frequently Asked Questions

What is CVE-2022-24817?
CVE-2022-24817 is a security vulnerability in Github.com/fluxcd/flux2 involving Improper kubeconfig validation allows arbitrary code execution under CWE-94: Improper Control of Generation of Code ('Code Injection').
Which Github.com/fluxcd/flux2 versions are affected?
Affected versions include releases prior to 0.29.0, 0.23.0, 0.19.0 across affected packages: github.com/fluxcd/flux2, github.com/fluxcd/kustomize-controller, github.com/fluxcd/helm-controller.
What version fixes CVE-2022-24817?
Upgrading to 0.29.0, 0.23.0, 0.19.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/fluxcd/flux2 affected?
Yes, github.com/fluxcd/flux2 is affected in releases prior to 0.29.0. Upgrade your dependency to 0.29.0 or later.
Is github.com/fluxcd/kustomize-controller affected?
Yes, github.com/fluxcd/kustomize-controller is affected in releases prior to 0.23.0. Upgrade your dependency to 0.23.0 or later.
What is the CVSS score of CVE-2022-24817?
CVE-2022-24817 has a CVSS v3.1 base score of 9.9 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2022-24817?
CVE-2022-24817 is classified under CWE-94: Improper Control of Generation of Code ('Code Injection') (The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.).
How can I check Go dependencies for CVE-2022-24817?
Run the dependency tree command: 'inspect dependencies for github.com/fluxcd/flux2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vvmq-fwmg-2gjc",
  "modified" : "2022-05-26T20:07:54Z",
  "published" : "2022-05-16T18:13:51Z",
  "aliases" : [ "CVE-2022-24817" ],
  "summary" : "Improper kubeconfig validation allows arbitrary code execution",
  "details" : "Flux2 can reconcile the state of a remote cluster when provided with a [kubeconfig](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/#file-references) with the correct access rights. `Kubeconfig` files can define [commands](https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins) to be executed to generate on-demand authentication tokens. A malicious user with write access to a Flux source or direct access to the target cluster, could craft a `kubeconfig` to execute arbitrary code inside the controller’s container.\n\nIn multi-tenancy deployments this can also lead to privilege escalation if the controller's service account has elevated permissions.\n\n### Impact\n\nWithin the affected versions range, one of the permissions set below would be required for the vulnerability to be exploited:\n- Direct access to the cluster to create Flux `Kustomization` or `HelmRelease` objects and Kubernetes Secrets.\n- Direct access to the cluster to modify existing Kubernetes secrets being used as `kubeconfig` in existing Flux `Kustomization` or `HelmRelease` objects.\n- Direct access to the cluster to modify existing Flux `Kustomization` or `HelmRelease` objects and access to create or modify existing Kubernetes secrets.\n- Access rights to make changes to a configured Flux Source (i.e. Git repository).\n\n### Patches\n\nThis vulnerability was fixed in kustomize-controller [v0.23.0](https://github.com/fluxcd/kustomize-controller/releases/tag/v0.23.0) and helm-controller [v0.19.0](https://github.com/fluxcd/helm-controller/releases/tag/v0.19.0), both included in flux2 [v0.29.0](https://github.com/fluxcd/flux2/releases/tag/v0.29.0). Starting from the fixed versions, both controllers disable the use of command execution from `kubeconfig` files by default, users have to opt-in by adding the flag `--insecure-kubeconfig-exec` to the controller’s command arguments. Users are no longer allowed to refer to files in the controller’s filesystem in the `kubeconfig` files provided for the remote apply feature.\n\n### Workarounds\n\n- The functionality can be disabled via Validating Admission webhooks (e.g. OPA Gatekeeper, Kyverno) by restricting users from being able to set the `spec.kubeConfig` field in Flux `Kustomization` and `HelmRelease` objects.\n- Applying restrictive AppArmor and SELinux profiles on the controller’s pod to limit what binaries can be executed.\n\n### Credits\n\nThe Flux engineering team found and patched this vulnerability.\n\n### For more information\n\nIf you have any questions or comments about this advisory please open an issue in the [flux2 repository](http://github.com/fluxcd/flux2).\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/fluxcd/flux2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.1.0"
      }, {
        "fixed" : "0.29.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/fluxcd/kustomize-controller"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.1.0"
      }, {
        "fixed" : "0.23.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/fluxcd/helm-controller"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.2.0"
      }, {
        "fixed" : "0.19.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/fluxcd/flux2/security/advisories/GHSA-vvmq-fwmg-2gjc"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-24817"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/fluxcd/flux2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-94" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-05-16T18:13:51Z",
    "nvd_published_at" : "2022-05-06T00:15:00Z"
  }
}