Rust advisories / curve25519-dalek
Vulnerability LowRUSTSEC-2024-0344 · curve25519-dalek
RUSTSEC-2024-0344: Timing variability in `curve25519-dalek`'s `Scalar29::sub`/`Scalar52::sub`
Short answerA security vulnerability in the curve25519-dalek crate: Timing variability in `curve25519-dalek`'s `Scalar29::sub`/`Scalar52::sub`. GitHub rates it Low. Fixed in 4.1.3: update to a fixed version.
| Crate | curve25519-dalek |
|---|---|
| Type | Vulnerability (crypto-failure) |
| Affected versions | Before 4.1.3. |
| Fixed in | 4.1.3 |
| Severity | Low (GitHub rating) |
| Published | 2024-06-18 |
| Last changed | 2025-10-28 |
| Also known as | CVE-2024-58262, GHSA-x4gp-pqpj-f43q |
What to do
- See which version you have:
cargo tree -i curve25519-dalek(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p curve25519-dalek. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplecurve25519-dalek = "4.1.3") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Timing variability of any kind is problematic when working with potentially secret values such as elliptic curve scalars, and such issues can potentially leak private keys and other secrets. Such a problem was recently discovered in curve25519-dalek.
The Scalar29::sub (32-bit) and Scalar52::sub (64-bit) functions contained usage of a mask value inside a loop where LLVM saw an opportunity to insert a branch instruction (jns on x86) to conditionally bypass this code section when the mask value is set to zero as can be seen in godbolt:
- 32-bit (see L106): <https://godbolt.org/z/zvaWxzvqv>
- 64-bit (see L48): <https://godbolt.org/z/PczYj7Pda>
A similar problem was recently discovered in the Kyber reference implementation:
<https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/hqbtIGFKIpU/m/cnE3pbueBgAJ>
As discussed on that thread, one portable solution, which is also used in this PR, is to introduce a volatile read as an optimization barrier, which prevents the compiler from optimizing it away.
The fix can be validated in godbolt here:
- 32-bit: <https://godbolt.org/z/jc9j7eb8E>
- 64-bit: <https://godbolt.org/z/x8d46Yfah>
The problem was discovered and the solution independently verified by Alexander Wagner <alexander.wagner@aisec.fraunhofer.de> and Lea Themint <lea.thiemt@tum.de> using their DATA tool:
<https://github.com/Fraunhofer-AISEC/DATA>
References
- Package: crates.io/crates/curve25519-dalek
- Advisory: rustsec.org/advisories/RUSTSEC-2024-0344.html
- Web: github.com/dalek-cryptography/curve25519-dalek/pull/659
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Same cratecurve25519-dalek: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?