RUSTSEC-2020-0003 json
rust_sodium is unmaintained; switch to a modern alternative
published 6y ago modified 6y ago
- 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
The `rust_sodium` crate is no longer maintained by its current owner, who advise in the repository readme that they are looking for someone else to take ownership of it.
We recommend you switch to an alternative crate such as: - [`sodiumoxide`](https://crates.io/crates/sodiumoxide)
Patch / fix
Is RUSTSEC-2020-0003 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 | rust_sodium | >=0.0.0-0, <0.10.3-0 |
0.10.3-0 |
References
Sources
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.