NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2023-32194: Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core'

highCVSS 4.0 8.6 · 3.1 7.2GHSA-c85r-fwc7-45vc

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.

Published Feb 8, 2024 · Updated May 23, 2025

Affected packages

github.com/rancher/rancher

Ecosystem
Go
Affected
>= 2.6.0, < 2.6.14
Fixed in
2.6.14
Check
go list -m github.com/rancher/rancher

github.com/rancher/rancher

Ecosystem
Go
Affected
>= 2.7.0, < 2.7.10
Fixed in
2.7.10
Check
go list -m github.com/rancher/rancher

github.com/rancher/rancher

Ecosystem
Go
Affected
>= 2.8.0, < 2.8.2
Fixed in
2.8.2
Check
go list -m github.com/rancher/rancher

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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 project or move another namespace into the project since the user doesn't have any permissions on namespaces in the core API group.

Moving a namespace to another project could lead to leakage of secrets, in case the targeted project has secrets. And also can lead to the namespace being able to abuse the resource quotas of the targeted project.

Patches

Patched versions include releases 2.6.14, 2.7.10 and 2.8.2.

Workarounds

There is no direct mitigation besides updating Rancher to a patched version.

References

If you have any questions or comments about this advisory:

Credited to AnonySE26.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries