Cyber Resilience

CVE-2024-58262

Curve25519-Dalek ≤ 4.1.3

Published
27 July 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 2.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0015 5th percentile
Risk Priority 25 floored blend · peak EPSS

Summary

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

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

T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1497 Virtualization/Sandbox Evasion Stealth
Adversaries may employ various means to detect and avoid virtualization and analysis environments.
T1622 Debugger Evasion Stealth
Adversaries may employ various means to detect and avoid debuggers.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-52496Shared CWE-733
CVE-2025-20241Shared CWE-733
CVE-2025-13024Shared CWE-733
CVE-2026-10702Shared CWE-733
CVE-2026-4698Shared CWE-733
CVE-2026-12299Shared CWE-733
CVE-2026-8389Shared CWE-733

Affected Assets

dalek
curve25519-dalek
≤ 4.1.3

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.

PR.PS-06 mostly match
prevents

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.

finds

Security testing in development can detect optimization-induced removal of security mechanisms.

prevents

Secure SDLC requires compiler and build-process controls that can prevent optimization removal of security code.

prevents

Secure coding standards explicitly address compiler flags and volatile/optimization barriers for security-critical code.

References