A vulnerability was found in dexidp dex 2.37.0. It has been rated as problematic. Affected by this issue is some unknown processing of the file cmd/dex/serve.go. The manipulation with an unknown input leads to a inadequate encryption vulnerability. Using CWE to declare the problem leads to CWE-326. The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. Impacted is confidentiality. CVE summarizes:

Dex is an identity service that uses OpenID Connect to drive authentication for other apps. Dex 2.37.0 serves HTTPS with insecure TLS 1.0 and TLS 1.1. `cmd/dex/serve.go` line 425 seemingly sets TLS 1.2 as minimum version, but the whole `tlsConfig` is ignored after `TLS cert reloader` was introduced in v2.37.0. Configured cipher suites are not respected either. This issue is fixed in Dex 2.38.0.

The weakness was disclosed 01/25/2024 as 2848. The advisory is available at github.com. This vulnerability is handled as CVE-2024-23656 since 01/19/2024. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1600 by the MITRE ATT&CK project.

Upgrading to version 2.38.0 eliminates this vulnerability. Applying the patch 5bbdb4420254ba73b9c4df4775fe7bdacf233b17 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The entries VDB-50396, VDB-166890, VDB-176048 and VDB-176978 are pretty similar.

Productinfo

Vendor

• dexidp

Name

• dex

Version

• 2.37.0

License

• open-source

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion