CVE-2023-32194
published 2024-10-16CVE-2023-32194: A vulnerability has been identified when granting a create or * global role for a resource type of "namespaces"; no matter the API group, the subject will…
PriorityP341high7.2CVSS 3.1
AVNACLPRHUINSUCHIHAH
EPSS
0.40%
32.1th percentile
A vulnerability has been identified when granting a create or * global role for a resource type of "namespaces"; no matter the API group, the subject will receive *
permissions for core namespaces. This can lead to someone being capable
of accessing, creating, updating, or deleting a namespace in the
project.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| github.com | rancher_rancher | >= 2.6.0 < 2.6.14 | 2.6.14 |
| github.com | rancher_rancher | >= 2.7.0 < 2.7.10 | 2.7.10 |
| github.com | rancher_rancher | >= 2.8.0 < 2.8.2 | 2.8.2 |
| suse | rancher | >= 2.6.0 < 2.6.14 | 2.6.14 |
| suse | rancher | >= 2.7.0 < 2.7.10 | 2.7.10 |
| suse | rancher | >= 2.8.0 < 2.8.2 | 2.8.2 |
CVSS provenance
nvdv3.17.2HIGHCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
nvdv4.08.6HIGHCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core' in github.com/rancher/rancher
osv·2024-06-28
CVE-2023-32194 Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core' in github.com/rancher/rancher
Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core' in github.com/rancher/rancher
Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core' in github.com/rancher/rancher.
NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.
(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)
The additional affected modules and versions are: github.com/rancher/rancher from v2.6.0 before v2.6.14, from v2.7.0 before v2.7.10, from v2.8.0 before v2.8.2.
OSV
Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core'
osv·2024-02-08
CVE-2023-32194 [HIGH] Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core'
Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core'
### Impact
A vulnerability has been identified when granting a `create` or `*` **global role** for a resource type of "namespaces"; no matter the API group, the subject will receive `*` permissions for core namespaces. This can lead to someone being capable of accessing, creating, updating, or deleting a namespace in the project. This includes reading or updating a namespace in the project so that it is available in other projects in which the user has the "manage-namespaces" permission or updating another namespace in which the user has normal "update" permissions to be moved into the project.
The expected behavior is to not be able to create, update, or delete a namespace in the proje
GHSA
Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core'
ghsa·2024-02-08
CVE-2023-32194 [HIGH] CWE-269 Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core'
Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core'
### Impact
A vulnerability has been identified when granting a `create` or `*` **global role** for a resource type of "namespaces"; no matter the API group, the subject will receive `*` permissions for core namespaces. This can lead to someone being capable of accessing, creating, updating, or deleting a namespace in the project. This includes reading or updating a namespace in the project so that it is available in other projects in which the user has the "manage-namespaces" permission or updating another namespace in which the user has normal "update" permissions to be moved into the project.
The expected behavior is to not be able to create, update, or delete a namespace in the proje
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-10-16
Published