PT-2025-35331 · Suse · Suse Fleet
Published
2025-08-29
·
Updated
2025-09-01
·
CVE-2024-52284
7.7
High
Base vector | Vector | AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
Name of the Vulnerable Software and Affected Versions:
SUSE Fleet versions prior to v0.14.0
SUSE Fleet version v0.13.1
SUSE Fleet version v0.12.6
SUSE Fleet version v0.11.10
Description:
A vulnerability exists in SUSE Fleet when managing Helm charts, where sensitive information passed through `BundleDeployment.Spec.Options.Helm.Values` may be stored in plain text. This can lead to unauthorized disclosure of sensitive data to users with `GET` or `LIST` permissions on `BundleDeployment` resources, and a lack of encryption at rest for these values. The issue arises because `BundleDeployment` is not configured for Kubernetes encryption at rest by default. This behavior differs from Helm v3’s default approach, where chart state is stored in Kubernetes secrets. The exposure of credentials can have varying impacts on confidentiality, integrity, and availability, depending on the permissions associated with the leaked credentials.
Recommendations:
Upgrade to SUSE Fleet version v0.14.0 or later.
Upgrade to SUSE Fleet version v0.13.1.
Upgrade to SUSE Fleet version v0.12.6.
Upgrade to SUSE Fleet version v0.11.10.
If upgrading is not possible, specify paths to valuesFiles as simple file names, for example, use `values.yaml` instead of `config-chart/values.yaml`.
Fix
Cleartext Storage of Sensitive Information
Weakness Enumeration
Related Identifiers
Affected Products
References · 8
- https://osv.dev/vulnerability/GHSA-6h9x-9j5v-7w9h · Vendor Advisory
- https://github.com/rancher/fleet/security/advisories/GHSA-6h9x-9j5v-7w9h⭐ 1632 🔗 245 · Note
- https://github.com/rancher/fleet⭐ 1632 🔗 245 · Note
- https://github.com/rancher/fleet/commit/088bcbea7edb844d7e6fc3649d9954f763cf68a9⭐ 1632 🔗 245 · Note
- https://twitter.com/CrowdCyber_Com/status/1962397949964488855 · Twitter Post
- https://twitter.com/the_yellow_fall/status/1962351206288015613 · Twitter Post
- https://t.me/pentestingnews/67272 · Telegram Post
- https://twitter.com/fridaysecurity/status/1962353048119886193 · Twitter Post