by @LeSuisse Activity log
- Created suggestion
- @LeSuisse ignored
- @LeSuisse ignored package traefik-certs-dumper
- @LeSuisse accepted
- @LeSuisse published on GitHub
Traefik Kubernetes CRD allows unauthorized cross-namespace middleware binding
Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is a potential vulnerability in Traefik's Kubernetes CRD provider cross-namespace isolation enforcement. When providers.kubernetesCRD.allowCrossNamespace=false, Traefik correctly rejects direct cross-namespace middleware references from IngressRoute objects, but fails to apply the same restriction to middleware references nested inside a Chain middleware's spec.chain.middlewares[]. An actor with permission to create or update Traefik CRDs in their own namespace can exploit this to cause Traefik to resolve and apply middleware objects from another namespace, bypassing the documented isolation boundary. This issue has been patched in versions 2.11.43, 3.6.14, and 3.7.0-rc.2.
References
-
https://github.com/traefik/traefik/security/advisories/GHSA-xhjw-95fp-8vgq x_refsource_CONFIRM
Ignored references (3)
-
https://github.com/traefik/traefik/releases/tag/v3.7.0-rc.2 x_refsource_MISC
-
https://github.com/traefik/traefik/releases/tag/v3.6.14 x_refsource_MISC
-
https://github.com/traefik/traefik/releases/tag/v2.11.43 x_refsource_MISC
Affected products
- ==>= 3.7.0-ea.1, < 3.7.0-rc.2
- ==< 2.11.43
Matching in nixpkgs
pkgs.traefik
Modern reverse proxy
-
nixos-unstable 3.7.0-ea.2
- nixpkgs-unstable 3.7.0-ea.2
- nixos-unstable-small 3.7.0-ea.2
Package maintainers
-
@vdemeester Vincent Demeester <vincent@sbr.pm>
-
@djds djds <git@djds.dev>