GHSA-978j-88f3-p5j3 json
Threshold value is ignored (all shares are n=3)
published 6y ago modified 3y ago also RUSTSEC-2020-0160
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io shamir 2.0.0
Is GHSA-978j-88f3-p5j3 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | shamir | <2.0.0 >=0.0.0-0, <2.0.0 |
2.0.0 |
References
-
github.com
/Nebulosus/shamir/issues/3
web, report
-
github.com
/Nebulosus/shamir
package
-
rustsec.org
/advisories/RUSTSEC-2020-0160.html
web, advisory
-
crates.io
/crates/shamir
package
Sources
- GitHub Advisory GHSA-978j-88f3-p5j3
- OSV RUSTSEC-2020-0160
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.