Authentication bypass using an empty token in capsule-proxy
projectcapsule capsule-proxy
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/projectcapsule/capsule-proxy Go |
|
|
| github.com/clastix/capsule-proxy Go |
|
|
projectcapsule capsule-proxy
| Product | Affected | Fixed in |
|---|---|---|
| github.com/projectcapsule/capsule-proxy Go |
|
|
| github.com/clastix/capsule-proxy Go |
|
|
capsule-proxy is a reverse proxy for the capsule operator project. Affected versions are subject to a privilege escalation vulnerability which is based on a missing check if the user is authenticated based on the `TokenReview` result. All the clusters running with the `anonymous-auth` Kubernetes API Server setting disable (set to `false`) are affected since it would be possible to bypass the token review mechanism, interacting with the upper Kubernetes API Server. This privilege escalation cannot be exploited if you're relying only on client certificates (SSL/TLS). This vulnerability has been addressed in version 0.4.6. Users are advised to upgrade.
From the CVE record · GitHub_M
Affected capsule-proxy versions fail to check whether a user is authenticated in the TokenReview result. An attacker can bypass token review and escalate privileges when the Kubernetes API server has anonymous-auth disabled. The vulnerability cannot be exploited when authentication relies only on client certificates.
Teams running github.com/projectcapsule/capsule-proxy or github.com/clastix/capsule-proxy versions earlier than 0.4.6 should check their deployments.