This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate stronghold_engine

Dependencies

(9 total, 2 outdated)

CrateRequiredLatestStatus
 thiserror^1.01.0.30up to date
 anyhow^1.01.0.52up to date
 dirs-next^2.02.0.0up to date
 hex^0.4.20.4.3up to date
 paste^1.0.11.0.6up to date
 once_cell^1.41.9.0up to date
 serde^1.01.0.133up to date
 digest^0.9.00.10.1out of date
 iota-crypto^0.8.00.9.1out of date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 tempfile^3.1.03.3.0up to date
 proptest^1.0.01.0.0up to date
 criterion^0.3.30.3.5up to date
 json^0.120.12.4up to date

Crate stronghold-runtime

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 libsodium-sys^0.20.2.7up to date
 serde^1.01.0.133up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 quickcheck^1.01.0.3up to date

Crate iota_stronghold

Dependencies

(11 total, 2 outdated)

CrateRequiredLatestStatus
 bincode^1.31.3.3up to date
 serde^1.01.0.133up to date
 zeroize^1.11.5.0up to date
 zeroize_derive^1.01.3.1up to date
 anyhow^1.01.0.52up to date
 thiserror^1.01.0.30up to date
 futures^0.30.3.19up to date
 actix^0.120.12.0up to date
 rand^0.8.30.8.4up to date
 hkdf^0.110.12.0out of date
 iota-crypto^0.8.00.9.1out of date

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 hex^0.4.20.4.3up to date
 criterion^0.3.30.3.5up to date
 clap^3.0.0-rc.43.0.10up to date
 tokio ⚠️^1.91.15.0maybe insecure

Crate stronghold-utils

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 rand^0.8.30.8.4up to date

Crate stronghold-derive

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 syn^1.01.0.85up to date
 quote^1.01.0.14up to date
 proc-macro2^1.01.0.36up to date

Crate stronghold-p2p

Dependencies

(9 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.30.3.19up to date
 libp2p^0.41.00.41.1up to date
 pin-project^1.0.81.0.10up to date
 serde^1.01.0.133up to date
 serde_json^1.01.0.75up to date
 smallvec^1.6.11.8.0up to date
 thiserror^1.0.301.0.30up to date
 tokio ⚠️^1.101.15.0maybe insecure
 wasm-timer^0.2.50.2.5up to date

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-rt^2.52.6.0up to date
 regex^1.51.5.4up to date
 tokio ⚠️^1.101.15.0maybe insecure
 libp2p^0.41.00.41.1up to date

Security Vulnerabilities

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.