Traefik before 3.6.23 IngressRouteTCP ServersTransport Namespace Bypass
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.6.23, 3.7.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- traefik traefik
From 3.6.0 · fixed in 3.6.23
- traefik traefik
From 3.7.0 · fixed in 3.7.7
- github.com/traefik/traefik/v3Go
From 3.6.0 · fixed in 3.6.23
- github.com/traefik/traefik/v3Go
From 3.7.0 · fixed in 3.7.7
- github.com/traefik/traefikGo
All versions
- github.com/traefik/traefik/v2Go
All versions
- github.com/traefik/traefik/v3Go
From 3.6.0 · fixed in 3.6.23; From 3.7.0 · fixed in 3.7.7