CVE-2024-52282 json
Rancher Helm Applications may have sensitive values leaked
published last yr. modified 2mo ago also GHSA-9c5p-35gj-jqp4 , GO-2024-3280 , EUVD-2024-3351
- cvss
- 6.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/rancher/rancher 2.8.10, 2.9.4
- SUSE rancher 2.8.10, 2.9.4
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20241121T195252-1.1
opensuse advisories openSUSE-SU-2024:14519-1
Is CVE-2024-52282 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N |
| GitHub | 3.1 | 6.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/rancher/rancher | >=2.8.0, <2.8.10 >=2.9.0, <2.9.4 all versions |
2.8.10 2.9.4 |
Affected products
- SUSE rancher
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
Sources
- CVE List CVE-2024-52282
- GitHub Advisory GHSA-9c5p-35gj-jqp4
- NVD CVE-2024-52282
- OSV GO-2024-3280
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.