Portainer: Kubernetes middleware continues after token validation failure, bypassing endpoint authorization
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| portainer | portainer | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Portainer | Portainer |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-mgq6-4x29-88r3 | Portainer's Kubernetes middleware continues after token validation failure, bypassing endpoint authorization |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.335% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:portainer:portainer:*:*:*:*:community:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Portainer
Portainer portainer |
|
| Vendors & Products |
Portainer
Portainer portainer |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Portainer Community Edition is a lightweight service delivery platform for containerized applications that can be used to manage Docker, Swarm, Kubernetes and ACI environments. From 2.33.0 to before 2.33., Portainer proxies requests to Kubernetes clusters through a middleware layer (kubeClientMiddleware) that validates the requesting user's token before forwarding traffic to the cluster. When security.RetrieveTokenData returned an error, the middleware wrote an HTTP 403 response but was missing a return statement — execution continued into the handler with a nil tokenData value. The Kubernetes endpoints sit behind Portainer's outer AuthenticatedAccess bouncer, so an attacker requires a valid Portainer session. However, a user whose secondary token validation fails in kubeClientMiddleware — for example a user without permission to access a given Kubernetes endpoint — would have their request forwarded to the cluster anyway, bypassing the authorization check. The same defect was present in both the CE and EE codebases. This vulnerability is fixed in 2.33.8. | |
| Title | Portainer: Kubernetes middleware continues after token validation failure, bypassing endpoint authorization | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|