Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-hrhx-6h34-j5hc
No affected components available
Impact
People that configure mTLS between Traefik and clients.
For a request, the TLS configuration choice can be different than the router choice, which implies the use of a wrong TLS configuration.
-
When sending a request using FQDN handled by a router configured with a dedicated TLS configuration, the TLS configuration falls back to the default configuration that might not correspond to the configured one.
-
If the CNAME flattening is enabled, the selected TLS configuration is the SNI one and the routing uses the CNAME value, so this can skip the expected TLS configuration.
Patches
Traefik v2.6.x: https://github.com/traefik/traefik/releases/tag/v2.6.1
Workarounds
Add the FDQN to the host rule:
Example:
whoami:
image: traefik/whoami:v1.7.1
labels:
traefik.http.routers.whoami.rule: Host(`whoami.example.com`, `whoami.example.com.`)
traefik.http.routers.whoami.tls: true
traefik.http.routers.whoami.tls.options: mtls@file
There is no workaround if the CNAME flattening is enabled.
For more information
If you have any questions or comments about this advisory, please open an issue.
The vulnerability can be exploited over the network without needing physical access. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard