Headline
GHSA-c7xh-gjv4-4jgv: kcp's impersonation allows access to global administrative groups
Impact
Impersonation is a feature of the Kubernetes API, allowing to override user information. As downstream project, kcp inherits this feature. As per the linked documentation a specific level of privilege (usually assigned to cluster admins) is required for impersonation.
The vulnerability in kcp affects kcp installations in which users are granted the cluster-admin ClusterRole (or comparably high permission levels that grant impersonation access; the verb in question is impersonate) within their respective workspaces. As kcp builds around self-service confined within workspaces, most installations would likely grant such workspace access to their users. Such users can impersonate special global administrative groups, which circumvent parts of the authorizer chains, e.g. maximal permission policies.
Patches
The problem has been patched in #3206 and is available in kcp 0.26.1 and higher.
Workarounds
- Not assigning the
cluster-adminrole (or any other role granting blanket impersonation permissions) to users. - A reverse proxy between users and kcp to check for the
Impersonate-Groupheader and reject requests that impersonate global administrative groups.
References
See the pull request (#3206).
Impact
Impersonation is a feature of the Kubernetes API, allowing to override user information. As downstream project, kcp inherits this feature. As per the linked documentation a specific level of privilege (usually assigned to cluster admins) is required for impersonation.
The vulnerability in kcp affects kcp installations in which users are granted the cluster-admin ClusterRole (or comparably high permission levels that grant impersonation access; the verb in question is impersonate) within their respective workspaces. As kcp builds around self-service confined within workspaces, most installations would likely grant such workspace access to their users. Such users can impersonate special global administrative groups, which circumvent parts of the authorizer chains, e.g. maximal permission policies.
Patches
The problem has been patched in #3206 and is available in kcp 0.26.1 and higher.
Workarounds
- Not assigning the cluster-admin role (or any other role granting blanket impersonation permissions) to users.
- A reverse proxy between users and kcp to check for the Impersonate-Group header and reject requests that impersonate global administrative groups.
References
See the pull request (#3206).
References
- GHSA-c7xh-gjv4-4jgv
- kcp-dev/kcp#3206
- kcp-dev/kcp@24ab5d4