CVE-2022-46153

Workarounds

Check the logs to detect the following error messages and fix your TLS options:

• Empty CA:

{"level":"error","msg":"invalid clientAuthType: RequireAndVerifyClientCert, CAFiles is required","routerName":"Router0@file"}

• Bad CA content (or bad path):

{"level":"error","msg":"invalid certificate(s) content","routerName":"Router0@file"}

• Unknown Client Auth Type:

{"level":"error","msg":"unknown client auth type \"FooClientAuthType\"","routerName":"Router0@file"}

• Invalid cipherSuites

{"level":"error","msg":"invalid CipherSuite: foobar","routerName":"Router0@file"}

• Invalid curvePreferences

{"level":"error","msg":"invalid CurveID in curvePreferences: foobar","routerName":"Router0@file"}

For more information

If you have any questions or comments about this advisory, please open an issue.

There is a potential vulnerability in Traefik managing the TLS connections.

A router configured with a not well-formatted TLSOption is exposed with an empty TLSOption.

For instance, a route secured using an mTLS connection set with a wrong CA file is exposed without verifying the client certificates.

CVE-2022-46153 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.9.6); upgrading removes the vulnerable code path.

Kodem intelligence

https://github.com/traefik/traefik/releases/tag/v2.9.6

1. What is CVE-2022-46153? CVE-2022-46153 is a medium-severity security vulnerability in github.com/traefik/traefik/v2 (go), affecting versions < 2.9.6. It is fixed in 2.9.6.
2. How severe is CVE-2022-46153? CVE-2022-46153 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/traefik/traefik/v2 are affected by CVE-2022-46153? github.com/traefik/traefik/v2 (go) versions < 2.9.6 is affected.
4. Is there a fix for CVE-2022-46153? Yes. CVE-2022-46153 is fixed in 2.9.6. Upgrade to this version or later.
5. Is CVE-2022-46153 exploitable, and should I be worried? Whether CVE-2022-46153 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-46153 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-46153? Upgrade github.com/traefik/traefik/v2 to 2.9.6 or later.

Other vulnerabilities in github.com/traefik/traefik/v2