Traefik has Knative Ingress Rule Injection that Allows Host Restriction Bypass
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
| No fix yet |
| github.com/traefik/traefik Go |
| No fix yet |
Traefik is an HTTP reverse proxy and load balancer. Prior to versions 3.6.11 and 3.7.0-ea.2, Traefik's Knative provider builds router rules by interpolating user-controlled values into backtick-delimited rule expressions without escaping. In live cluster validation, Knative `rules[].hosts[]` was exploitable for host restriction bypass (for example `tenant.example.com`) || Host(`attacker.com`), producing a router that serves attacker-controlled hosts. Knative `headers[].exact` also allows rule-syntax injection and proves unsafe rule construction. In multi-tenant clusters, this can route unauthorized traffic to victim services and lead to cross-tenant traffic exposure. Versions 3.6.11 and 3.7.0-ea.2 patch the issue.
From the CVE record · GitHub_M
Traefik's Knative provider inserts user-controlled host and header values into router rules without escaping them. An attacker who can control those values in a multi-tenant cluster can inject rule syntax, potentially routing unauthorized traffic to victim services and exposing cross-tenant traffic.
Teams running Go package github.com/traefik/traefik/v3 before 3.6.11 or from 3.7.0-ea.1 to before 3.7.0-ea.2, or any version of github.com/traefik/traefik/v2 or github.com/traefik/traefik, should check their deployments.