Portainer: Endpoint security bypass via Swarm service create/update
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 enforces seven EndpointSecuritySettings restrictions that administrators configure to restrict the container configurations non-admin users can launch: privileged mode, host PID namespace, device mapping, capabilities, sysctls, security-opt (Seccomp / AppArmor), and bind mounts. These restrictions are enforced on the standard container creation path, but several of them are not applied on the Docker Swarm service API. This vulnerability is fixed in 2.33.8, 2.39.2, and 2.41.0.
From the CVE record · GitHub_M
Portainer Community Edition does not apply some administrator-configured container restrictions on the Docker Swarm service API. An authenticated non-admin user who can use that API may launch services with configurations the administrator intended to restrict.
Teams running Portainer Community Edition versions 2.33.0 to before 2.33.8, 2.39.0 to before 2.39.2, or 2.40.0 to before 2.41.0 should check their deployments.