Gardener: Authorization Bypass via Group Subject Injection
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in github.com/gardener/gardener 1.142.6, github.com/gardener/gardener 1.143.3 and github.com/gardener/gardener 1.144.2.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| gardener | <1.142.6, >=1.143.0 <1.143.3, >=1.144.0 <1.144.2 | ||
| go: github.com/gardener/gardener | <1.142.6, >=1.143.0 <1.143.3, >=1.144.0 <1.144.2 | 1.142.6, 1.143.3, 1.144.2 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket