Vulnerability MediumRUSTSEC-2017-0001 · sodiumoxide
RUSTSEC-2017-0001: scalarmult() vulnerable to degenerate public keys
Short answerA security vulnerability in the sodiumoxide crate: scalarmult() vulnerable to degenerate public keys. Medium severity (CVSS 6.5). Fixed in 0.0.14: update to a fixed version.
| Crate | sodiumoxide |
|---|---|
| Type | Vulnerability |
| Affected versions | Before 0.0.14. |
| Fixed in | 0.0.14 |
| Severity | Medium, CVSS 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| Published | 2017-01-26 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2017-1000168, GHSA-2wc6-2rcj-8v76 |
What to do
- See which version you have:
cargo tree -i sodiumoxide(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p sodiumoxide. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplesodiumoxide = "0.0.14") 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
The scalarmult() function included in previous versions of this crate accepted all-zero public keys, for which the resulting Diffie-Hellman shared secret will always be zero regardless of the private key used.
This issue was fixed by checking for this class of keys and rejecting them if they are used.
References
- Package: crates.io/crates/sodiumoxide
- Advisory: rustsec.org/advisories/RUSTSEC-2017-0001.html
- Report: github.com/dnaq/sodiumoxide/issues/154
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for sodiumoxide
Up next
Same cratesodiumoxide: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?