Traefik: `allowCrossNamespace=false` bypass via `@kubernetescrd` TraefikService backendRef
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik/v3 Go |
|
|
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik Go |
| No fix yet |
Traefik is an open-source edge router that makes publishing services a fun and easy experience. Prior to 2.11.54, 3.6.25, and 3.7.10, cross-namespace @kubernetescrd references are not rejected for TraefikService backend references resolved by the service resolver. A tenant confined by RBAC to a single namespace can therefore bind its own router to a TraefikService owned by another namespace and expose or reroute that namespace's backend, defeating the namespace isolation allowCrossNamespace=false is meant to enforce. This issue is fixed in version 2.11.54, 3.6.25, 3.7.10.
From the CVE record · GitHub_M
Traefik fails to reject cross-namespace @kubernetescrd references to TraefikService backends, bypassing the isolation intended by allowCrossNamespace=false. A tenant with RBAC access limited to one namespace can bind its router to another namespace’s TraefikService and expose or reroute its backend.
Check deployments using Go github.com/traefik/traefik/v2 before 2.11.54, github.com/traefik/traefik/v3 from 3.0.0 to before 3.6.25 or from 3.7.0 to before 3.7.10, or github.com/traefik/traefik, for which no fixed version is listed.