CVE-2024-11022
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:LSummary
CVE-2024-11022 is a medium-severity Reusing a Nonce, Key Pair in Encryption (CWE-323) vulnerability in Sick (inferred from references). Its CVSS base score is 5.6 (Medium).
Operationally, ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-34047
Vulnerability Data
The authentication process to the web server uses a challenge response procedure which inludes the nonce and additional information. This challenge can be used several times for login and is therefore vulnerable for a replay attack.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.8.3V11.3.4
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover nonce reuse through static analysis, fuzzing, or known-answer tests.
Engineering principles include correct use of cryptographic primitives such as unique nonces per key.
Selecting and implementing appropriate cryptographic algorithms and modes reduces nonce-reuse exposure.
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.
Secure SDLC practices directly prevent nonce/key reuse errors in cryptographic implementations.
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.
Mandates proper cryptographic key and nonce management, directly preventing nonce/key-pair reuse.
Security testing can detect nonce reuse, yet the control addresses many other issues beyond this CWE.
Secure-coding rules can require unique nonces, but the control is broader than this single weakness.