Advisory

GHSA-c85r-fwc7-45vc

Also known as: CVE-2023-32194, GO-2024-2535

Summary

Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core'

Details

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:

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-02-08 18:43 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/rancher/rancher

Go · All systems

Affected

  • introduced 2.6.0, fixed 2.6.14 (semver)

Fixed versions

2.6.14

Fix

github.com/rancher/rancher

Go · All systems

Affected

  • introduced 2.7.0, fixed 2.7.10 (semver)

Fixed versions

2.7.10

Fix

github.com/rancher/rancher

Go · All systems

Affected

  • introduced 2.8.0, fixed 2.8.2 (semver)

Fixed versions

2.8.2

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences