Portainer vulnerabilities

Portainer Community Edition from version 2.33.0 to 2.33.8, 2.39.2, and 2.41.0 contains a vulnerability where, during creation or update of Git-backed stacks, go-git v5 creates OS symlinks on the host filesystem without validation, except for .gitmodules. An authenticated user with rights to manage Git stacks can include a docker-compose.yml file as a symlink to an arbitrary path, causing the GET /api/stacks/{id}/file endpoint to read and return the symlink target's contents in the HTTP response.

A vulnerability in Portainer Community Edition from version 2.33.0 to 2.33.7 allows writing files to arbitrary locations on the server filesystem via a crafted .tar.gz archive. The ExtractTarGz function does not prevent directory traversal, enabling overwriting of critical system files.

Portainer Community Edition versions 2.33.0 through 2.33.8, 2.39.2, and 2.41.0 accept JWT tokens via the ?token= URL parameter, leading to token leakage through proxy logs, browser history, and Referer headers. A leaked token grants full user privileges until expiration (default 8 hours).

In Portainer Community Edition from version 2.33.0 to 2.33.7, there is a vulnerability due to a missing return statement after a token validation error in the kubeClientMiddleware layer. This causes a request with an invalid token to be forwarded to the Kubernetes cluster, bypassing authorization checks.

Portainer Community Edition versions 2.33.0 through 2.33.7, 2.39.1, and 2.40.0 have a vulnerability in the Disable bind mounts security setting for non-administrators. The enforcement check only inspected the HostConfig.Binds array, ignoring the equivalent HostConfig.Mounts array, allowing authenticated users to mount arbitrary host paths into containers.

A vulnerability in Portainer Community Edition allows bypassing seven EndpointSecuritySettings restrictions when creating Docker Swarm services. These restrictions are enforced on the standard container creation path but not applied on the Swarm service API, enabling unprivileged users to launch containers with dangerous configurations.

In Portainer Community Edition versions 2.33.0 through 2.33.8, 2.39.2, and 2.41.0, the Docker plugin management endpoints (/plugins/*) were not registered with a handler. This allowed standard users with endpoint access to perform privileged plugin operations, including installing and enabling plugins, directly against the underlying Docker daemon.