Advisory

GHSA-q6c7-56cq-g2wm

Also known as: CVE-2024-22032, GO-2024-2932

Summary

Rancher's RKE1 Encryption Config kept in plain-text within cluster AppliedSpec

Details

Impact
This issue is only relevant to clusters provisioned using RKE1 with secrets encryption configuration enabled.

A vulnerability has been identified in which an RKE1 cluster keeps constantly reconciling when secrets encryption configuration is enabled (please see the RKE documentation). When reconciling, the Kube API secret values are written in plaintext on the AppliedSpec. Cluster owners, Cluster members, and Project members (for projects within the cluster), all have RBAC permissions to view the cluster object from the apiserver.

This could lead to an unauthorized user gaining access to the entire secrets encryption config specific for the cluster, only on the applied spec.

Since this affects only custom encryption configurations, users need to manually rotate the keys by editing the cluster. For more information, please refer to the RKE secrets encryption documentation.

The full custom configuration example:

services:
  kube-api:
    secrets_encryption_config:
      enabled: true
      custom_config:
        apiVersion: apiserver.config.k8s.io/v1
        kind: EncryptionConfiguration
        resources:
        - resources:
          - secrets
          providers:
          - aescbc:
              keys:
              - name: k-fw5hn
                secret: RTczRjFDODMwQzAyMDVBREU4NDJBMUZFNDhCNzM5N0I= #<--- needs to be changed
          - identity: {}

Please consult the associated MITRE ATT&CK - Technique - Unsecured Credentials for further information about this category of attack.

Patches
To address this issue, the fix introduces a new change that copies the AppliedSpec before mutating. As such, the next time the cluster is reconciled and the AppliedSpec is set, all references to sensitive data will be removed.

Patched versions include releases 2.7.14 and 2.8.5.

Workarounds
There are no workarounds for this issue. Users are recommended to upgrade, as soon as possible, to a version of RKE/Rancher Manager which contains the fixes.

References

If you have any questions or comments about this advisory:

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-06-17 22:30 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/rancher/rancher

Go · All systems

Affected

  • introduced 2.7.0, fixed 2.7.14 (semver)

Fixed versions

2.7.14

Fix

github.com/rancher/rancher

Go · All systems

Affected

  • introduced 2.8.0, fixed 2.8.5 (semver)

Fixed versions

2.8.5

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences