CVE-2022-21953 json
Authenticated user can gain unauthorized shell pod and kubectl access in the local cluster
published 3y ago modified 4mo ago also GHSA-g25r-gvq3-wrq7 , EUVD-2023-0463
- cvss
- 7.4
- 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 Missing Authorization vulnerability in of SUSE Rancher allows authenticated user to create an unauthorized shell pod and kubectl access in the local cluster This issue affects: SUSE Rancher Rancher versions prior to 2.5.17; Rancher versions prior to 2.6.10; Rancher versions prior to 2.7.1.
Patch / fix
- go github.com/rancher/rancher 2.5.17, 2.6.10, 2.7.1
- SUSE Rancher 2.5.17, 2.6.10, 2.7.1
Is CVE-2022-21953 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.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/rancher/rancher | >=2.5.0, <2.5.17 >=2.6.0, <2.6.10 >=2.7.0, <2.7.1 |
2.5.17 2.6.10 2.7.1 |
Affected products
- SUSE Rancher
Classification
References
-
bugzilla.suse.com
/show_bug.cgi?id=1199731
web, issue-tracking
-
github.com
/rancher/rancher/security/advisories/GHSA-g25r-gvq3-wrq7
web
-
nvd.nist.gov
/vuln/detail/CVE-2022-21953
advisory
-
github.com
/rancher/rancher
package
Sources
- CVE List CVE-2022-21953
- GitHub Advisory GHSA-g25r-gvq3-wrq7
- NVD CVE-2022-21953
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.