The Silent Fallback: Bypassing Traefik mTLS with CVE-2022-23632
Vulnerability ID: CVE-2022-23632
CVSS Score: 7.4
Published: 2022-02-17
A logic flaw in Traefik's TLS configuration selection allows attackers to bypass router-specific security settings, including Mutual TLS (mTLS) requirements, by forcing a fallback to the default configuration.
TL;DR
Traefik versions prior to 2.6.1 fail to apply specific TLS configurations (like mTLS enforcement) when handling certain FQDN requests. The system defaults to the global TLS config, which is often less secure. If your default config doesn't require client certificates, an attacker can bypass authentication entirely by simply asking nicely.
⚠️ Exploit Status: POC
Technical Details
- Attack Vector: Network (AV:N)
- CVSS v3.1: 7.4 (High)
- Impact: Security Bypass / Info Disclosure
- EPSS Score: 0.56%
- Exploit Status: PoC Available
- KEV Status: Not Listed
Affected Systems
- Traefik < 2.6.1
- Oracle Communications Unified Inventory Management 7.5.0
- Oracle Communications Order and Service Management 7.4.0
- Oracle Communications Order and Service Management 7.4.1
-
Traefik: < 2.6.1 (Fixed in:
2.6.1) -
Unified Inventory Management: 7.5.0 (Fixed in:
See Vendor Advisory)
Code Analysis
Commit: PR-8764
Fix: apply the same approach as the rules system on the TLS configuration choice
Refactored TLS configuration lookup to align with routing rules.
Exploit Details
- GitHub: Advisory and theoretical PoC details
Mitigation Strategies
- Software Update
- Configuration Hardening
Remediation Steps:
- Upgrade Traefik to version 2.6.1 or higher immediately.
- Review the 'default' TLS configuration in your static config. Ensure it is as restrictive as possible.
- If patching is impossible, modify the default TLS options to
clientAuth.clientAuthType: RequireAndVerifyClientCert. (Warning: This will enforce mTLS for ALL routers relying on the default config).
References
Read the full report for CVE-2022-23632 on our website for more details including interactive diagrams and full exploit analysis.
Top comments (0)