dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-52282

MEDIUM · 6.2 CVSS v3.1 Published 2025-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable

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
A Exposure of Sensitive Information to an Unauthorized Actor vulnerability in SUSE rancher allowing any users with GET access to the Rancher Manager Apps Catalog to read any sensitive information that are contained within the Apps’ values. Additionally, the same information leaks into auditing logs when the audit level is set to equal or above 2. This issue affects rancher: from 2.8.0 before 2.8.10, from 2.9.0 before 2.9.4.

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

This is an information disclosure vulnerability in SUSE Rancher where users with only GET (read) access to the Apps Catalog can read sensitive information such as passwords, API keys, or secrets embedded in app values/configuration. Additionally, this sensitive data leaks into audit logs when the audit level is set to 2 or higher, exposing secrets to anyone with access to those logs.

MitigationUpgrade rancher to version 2.8.10 or 2.9.4 or later to remediate this vulnerability. Review audit logs for evidence of unauthorized access and rotate any exposed credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Network
Complexity
Low
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify Rancher installation and version
    Access the Rancher UI and check the version displayed in the UI footer, or use the Rancher API endpoint /v1/management.cattle.io.setting/fleet-{"check"} to retrieve version information
    Affected if The installed Rancher version is lower than 2.8.10 or 2.9.4 (versions below these are affected)
  2. Verify Apps Catalog is accessible
    Navigate to the Apps section in the Rancher UI or check via API endpoint /v1/catalog.cattle.io.clusterrepo to confirm catalog resources exist
    Affected if Apps Catalog resources are present and accessible in the environment
  3. Determine if users have GET access to Apps Catalog
    Review user/role assignments in Rancher under Users & Authentication > Global Permissions, or query the API endpoint /v1/management.cattle.io.globalrolebindings to identify users with read-only access to catalog resources
    Affected if Any user account has only GET (read) permissions to Apps Catalog without elevated write privileges
  4. Check audit log configuration
    Inspect Rancher audit settings via the UI under Global Settings > Audit Log, or query the API endpoint /v1/management.cattle.io.setting with keys containing 'audit' to retrieve the audit level configuration
    Affected if The audit level is set to 2 or higher (level 2 captures request body including potential secrets)

You are affected if Rancher version is below 2.8.10 or 2.9.4, users have GET-only access to Apps Catalog, and audit logging is enabled at level 2 or higher, allowing exposure of embedded secrets.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade rancher to version 2.8.10 or 2.9.4 or later to remediate this vulnerability. Review audit logs for evidence of unauthorized access and rotate any exposed credentials.

Recommended fix High confidence

Upgrade to Rancher 2.8.10+ or 2.9.4+ (choose the appropriate release line based on your current version)

  1. 1. Identify the current Rancher version by checking the Rancher UI (top-left corner) or running: kubectl get rancher -n cattle-system -o jsonpath='{.items[0].status.version}'
  2. 2. Determine the appropriate upgrade path: if on 2.8.x, upgrade to 2.8.10 or later; if on 2.9.x, upgrade to 2.9.4 or later
  3. 3. Create a complete backup of the Rancher environment including etcd snapshots and Kubernetes resources
  4. 4. Review SUSE Rancher upgrade documentation for your deployment type (single-node or HA)
  5. 5. Test the upgrade in a non-production environment first to verify compatibility
  6. 6. Schedule a maintenance window as upgrades may cause brief service interruptions
  7. 7. Execute the upgrade following SUSE documentation - for single-node: stop Rancher container, pull new image, start container; for HA: update Helm values and run helm upgrade
  8. 8. After upgrade completes, verify the Rancher UI is accessible and all clusters are connected
Caveat Standard upgrade risks apply - test in staging first; minor version upgrades within the same major.minor typically have minimal breaking changes

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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