Portainer: JWT accepted in URL query leaks tokens to logs and referers
portainer
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/portainer/portainer Go |
|
|
portainer
| Product | Affected | Fixed in |
|---|---|---|
| github.com/portainer/portainer Go |
|
|
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.8, 2.39.2, and 2.41.0, Portainer's authentication middleware accepts JWT bearer tokens passed as the ?token=<JWT> URL query parameter on any authenticated API endpoint, in addition to the standard Authorization: Bearer header. URLs are recorded in reverse-proxy access logs, browser history, and HTTP Referer headers on outbound navigation, so any JWT passed this way can be harvested by anyone with access to those logs or by an external site the user subsequently visits. A leaked token grants the full privileges of the user it was issued to, until the token expires (default 8 hours, configurable). The ?token= parameter was used by Portainer's browser-based container attach, exec, and pod shell features, so any user with exec or attach rights on a container was exposed — not only administrators. This vulnerability is fixed in 2.33.8, 2.39.2, and 2.41.0.
From the CVE record · GitHub_M
Portainer Community Edition accepts JWTs in URL query parameters on authenticated API endpoints. Those URLs can appear in proxy logs, browser history, or Referer headers; someone with access to the logs or an external site the user visits can obtain a token and use that user's privileges until it expires. Users with container exec or attach rights are exposed, not just administrators.
Teams running Portainer Community Edition or github.com/portainer/portainer versions >=2.33.0 <2.33.8, >=2.39.0 <2.39.2, or >=2.40.0 <2.41.0 should check their deployments.