CVE-2024-58262
Curve25519-Dalek ≤ 4.1.3
Raw vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2024-58262 is a low-severity Compiler Optimization Removal or Modification of Security-critical Code (CWE-733) vulnerability in Dalek Curve25519-Dalek. Its CVSS base score is 2.9 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 5th 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-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-54823
Vulnerability Data
The curve25519-dalek crate before 4.1.3 for Rust has a constant-time operation on elliptic curve scalars that is removed by LLVM.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can reveal cases where security code has been optimized away.
Documented developer processes and standards can mandate coding patterns and compiler flags that preserve security-critical operations.
Security engineering principles include requirements for correct implementation of protection mechanisms that survive compilation.
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 require techniques that preserve security-critical code against compiler optimizations.
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.
Security testing in development can detect optimization-induced removal of security mechanisms.
Secure SDLC requires compiler and build-process controls that can prevent optimization removal of security code.
Secure coding standards explicitly address compiler flags and volatile/optimization barriers for security-critical code.