Traefik: TCP readTimeout bypass via STARTTLS on Postgres
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. Prior to 3.6.8, there is a potential vulnerability in Traefik managing STARTTLS requests. An unauthenticated client can bypass Traefik entrypoint respondingTimeouts.readTimeout by sending the 8-byte Postgres SSLRequest (STARTTLS) prelude and then stalling, causing connections to remain open indefinitely, leading to a denial of service. This vulnerability is fixed in 3.6.8.
From the CVE record · GitHub_M
Traefik before 3.6.8 can leave connections open indefinitely when handling PostgreSQL STARTTLS requests. An unauthenticated network client can send an SSLRequest prelude and then stall, bypassing the entrypoint read timeout and potentially causing a denial of service. No user interaction is required.
Teams running Traefik or using Go packages github.com/traefik/traefik/v3 before 3.6.8, github.com/traefik/traefik, or github.com/traefik/traefik/v2 should check their deployments.