Gardener: Authorization Bypass via Group Subject Injection
gardener
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/gardener/gardener Go |
|
|
gardener
| Product | Affected | Fixed in |
|---|---|---|
| github.com/gardener/gardener Go |
|
|
Gardener implements the automated management and operation of Kubernetes clusters as a service. Prior to 1.142.6, 1.143.3, 1.144.2, and 1.145.0, the customverbauthorizer admission plugin's mustCheckProjectMembers manage-members check compares changes to User subjects but does not account for Group or ServiceAccount subjects in Project.spec.members. A project administrator who lacks manage-members permission can add arbitrary Group or ServiceAccount subjects, including the system:authenticated Group, and thereby grant broad project access. The resulting access can include Shoots, Secrets, and cloud provider credentials. This issue is fixed in versions 1.142.6, 1.143.3, 1.144.2, and 1.145.0.
From the CVE record · GitHub_M
Gardener’s customverbauthorizer admission plugin does not apply its manage-members check to Group or ServiceAccount subjects in project membership changes. An authenticated project administrator without manage-members permission can add those subjects, potentially granting broad access to Shoots, Secrets, and cloud provider credentials. No user interaction is described.
Teams running Gardener versions prior to 1.142.6, 1.143.3, 1.144.2, or 1.145.0 should check their deployments.