Traffic decryption via discarded TLS configuration
Published Jan 25, 2024 · Updated Jun 3, 2025
Inadequate encryption in Dex 2.37.0 allows remote attackers to decrypt HTTPS traffic by negotiating TLS 1.0 or TLS 1.1. The HTTPS server in cmd/dex/serve.go sets a TLS 1.2 minimum, but the certificate reloader discards that configuration and its cipher-suite restrictions. Exploitation requires the HTTPS listener and a client using a deprecated protocol; the reported consequence is disclosure of traffic to Dex.
Summary
What happened
Inadequate encryption in Dex 2.37.0 allows remote attackers to decrypt HTTPS traffic by negotiating TLS 1.0 or TLS 1.1. The HTTPS server in cmd/dex/serve.go sets a TLS 1.2 minimum, but the certificate reloader discards that configuration and its cipher-suite restrictions. Exploitation requires the HTTPS listener and a client using a deprecated protocol; the reported consequence is disclosure of traffic to Dex.
The record
- CVE
- CVE-2024-23656
- Published
- Jan 25, 2024
- Updated
- Jun 3, 2025
- Vendor
- Dex
- Product
- Dex
- Classifications
- CWE-757, CWE-326, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 25, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion== 2.37.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream TLS negotiation proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo