Rust advisories / shamir
Vulnerability LowRUSTSEC-2020-0160 · shamir
RUSTSEC-2020-0160: Threshold value is ignored (all shares are n=3)
Short answerA security vulnerability in the shamir crate: Threshold value is ignored (all shares are n=3). GitHub rates it Low. Fixed in 2.0.0: update to a fixed version.
| Crate | shamir |
|---|---|
| Type | Vulnerability (crypto-failure) |
| Affected versions | Before 2.0.0. |
| Fixed in | 2.0.0 |
| Severity | Low (GitHub rating) |
| Published | 2020-01-21 |
| Last changed | 2023-11-08 |
| Also known as | GHSA-978j-88f3-p5j3 |
What to do
- See which version you have:
cargo tree -i shamir(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p shamir. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleshamir = "2.0.0") 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
Affected versions of this crate did not properly calculate secret shares requirements.
This reduces the security of the algorithm by restricting the crate to always using a threshold value of three, rather than a configurable limit.
The flaw was corrected by correctly configuring the threshold.
References
- Package: crates.io/crates/shamir
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0160.html
- Report: github.com/Nebulosus/shamir/issues/3
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
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?