Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-23656 is a high-severity Inadequate Encryption Strength (CWE-326) vulnerability in Linuxfoundation Dex. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 36th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-0360
Vulnerability Data
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`…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 3 OS baselines
V12.1.1V12.2.1V12.3.3V17.2.2
Mitigating Controls (NIST 800-53 r5) AI
SC-13 requires selection and implementation of specific cryptographic algorithms and key lengths, directly preventing use of inadequate encryption strength.
SC-12 governs cryptographic key establishment and management, which can enforce sufficient key sizes and thereby reduce inadequate encryption strength.
Requiring protection of transmitted confidentiality and integrity forces selection of sufficiently strong negotiated algorithms rather than weaker ones.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.AA-04 addresses protection/verification of identity assertions in SSO/federation contexts while CWE-757 concerns protocol-level crypto algorithm negotiation, so the control neither prevents nor meaningfully mitigates the weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requiring the organization to define and enforce minimum cryptographic strength prevents deployment of insufficient key lengths or weak ciphers that can be brute-forced.
Secure SDLC practices include selecting strong crypto algorithms during design and implementation.
Application security requirements can specify minimum cryptographic strength to avoid downgrades.
A.8.27 mandates security-by-design principles (including least functionality, assume-breach, distrust-external-input, and selection of strong cryptography) plus design reviews against known attack patterns; this reaches the subset of algorithm-downgrade flaws that arise from missing or misapplied protocol-level choices, but leaves the dominant implementation-time and negotiation-logic cases (e.g. library defaults, missing minimum-strength enforcement) untouched.
Secure coding standards can mandate checks to reject weaker negotiated algorithms.
Security testing can detect and block algorithm downgrade vulnerabilities before deployment.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Windows 10 (1 rule)
- V-220938 The LanMan authentication level must be set to send NTLMv2 response only, and to refuse LM and NTLM. blocks CWE-757
Windows Server 2016 (1 rule)
- V-225054 The LAN Manager authentication level must be set to send NTLMv2 response only and to refuse LM and NTLM. blocks CWE-757
Windows Server 2019 (1 rule)
- V-205919 Windows Server 2019 LAN Manager authentication level must be configured to send NTLMv2 response only and to refuse LM and NTLM. blocks CWE-757