Traefik has Inverted TLS Verification Logic in its ingress-nginx Provider
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik Go |
| No fix yet |
| github.com/traefik/traefik/v2 Go |
|
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 is an HTTP reverse proxy and load balancer. Versions 3.5.0 through 3.6.2 have inverted TLS verification logic in the nginx.ingress.kubernetes.io/proxy-ssl-verify annotation. Setting the annotation to "on" (intending to enable backend TLS certificate verification) actually disables verification, allowing man-in-the-middle attacks against HTTPS backends when operators believe they are protected. This issue is fixed in version 3.6.3.
From the CVE record · GitHub_M
In Traefik 3.5.0 through 3.6.2, setting the nginx.ingress.kubernetes.io/proxy-ssl-verify annotation to "on" disables backend TLS certificate verification instead of enabling it. When that annotation is set, an attacker able to intercept traffic to an HTTPS backend can conduct a man-in-the-middle attack.
Operators running Traefik 3.5.0 through 3.6.2, or using the Go packages github.com/traefik/traefik or github.com/traefik/traefik/v2, should check their deployments; no fixed version is listed for the latter two packages.