Traefik before 3.6.23 IngressRouteTCP ServersTransport Namespace Bypass
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik Go |
| No fix yet |
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik Go |
| No fix yet |
| github.com/traefik/traefik/v2 Go |
|
| No fix yet |
Traefik 3.6.0 through 3.6.22 and 3.7.0 through 3.7.6 fail to enforce the crossProviderNamespaces allowlist for IngressRouteTCP service serversTransport references (the allowlist was only enforced for HTTP serversTransport references). A low-privileged Kubernetes user in a namespace not listed in crossProviderNamespaces can set serversTransport: foo@file on an IngressRouteTCP service, causing Traefik to accept the forbidden cross-provider reference and use a file-provider TCPServersTransport — including privileged backend mTLS client certificates, SPIFFE identity, or PROXY-protocol settings. This is fixed in 3.6.23 and 3.7.7.
From the CVE record · VulnCheck
Traefik fails to enforce the crossProviderNamespaces allowlist for IngressRouteTCP service serversTransport references. A low-privileged Kubernetes user in a namespace outside the allowlist can set a cross-provider reference, causing Traefik to use a file-provider TCPServersTransport that may include privileged backend mTLS client certificates, SPIFFE identity, or PROXY-protocol settings.
Check deployments using Traefik 3.6.0–3.6.22 or 3.7.0–3.7.6, and users of the Go packages github.com/traefik/traefik or github.com/traefik/traefik/v2, for which no fixed version is listed.