CVE-2022-24817 Improper kubeconfig validation allows arbitrary code execution

2022-05-0600:00:14

CWE-94

GitHub_M

www.cve.org

9.9 High

CVSS3

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

LOW

User Interaction

NONE

Scope

CHANGED

Confidentiality Impact

HIGH

Integrity Impact

HIGH

Availability Impact

HIGH

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

9.9 High

AI Score

Confidence

High

0.001 Low

EPSS

Percentile

38.9%

JSON

Flux2 is an open and extensible continuous delivery solution for Kubernetes. Flux2 versions between 0.1.0 and 0.29.0, helm-controller 0.1.0 to v0.19.0, and kustomize-controller 0.1.0 to v0.23.0 are vulnerable to Code Injection via malicious Kubeconfig. In multi-tenancy deployments this can also lead to privilege escalation if the controller’s service account has elevated permissions. Workarounds include disabling functionality via Validating Admission webhooks by restricting users from setting the spec.kubeConfig field in Flux Kustomization and HelmRelease objects. Additional mitigations include applying restrictive AppArmor and SELinux profiles on the controller’s pod to limit what binaries can be executed. This vulnerability is fixed in kustomize-controller v0.23.0 and helm-controller v0.19.0, both included in flux2 v0.29.0

CNA Affected

[
  {
    "product": "flux2",
    "vendor": "fluxcd",
    "versions": [
      {
        "status": "affected",
        "version": "flux2 < v0.29.0 >= v0.1.0"
      },
      {
        "status": "affected",
        "version": "helm-controller < v0.23.0 >= v0.1.0"
      },
      {
        "status": "affected",
        "version": "kustomize-controller < v0.19.0 >= v0.2.0"
      }
    ]
  }
]