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 libp2p-tcp

Dependencies

(8 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^0.41.6.0out of date
 futures^0.10.3.30out of date
 get_if_addrs^0.5.30.5.3up to date
 libp2p-core ⚠️^0.8.00.41.2out of date
 log^0.4.10.4.21up to date
 tk-listen^0.2.00.2.1up to date
 tokio-io^0.10.1.13up to date
 tokio-tcp^0.10.1.4up to date

Dev dependencies

(1 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^0.11.36.0out of date

Security Vulnerabilities

libp2p-core: Failure to properly verify ed25519 signatures makes any signature valid

RUSTSEC-2019-0004

Affected versions of this crate did not properly verify ed25519 signatures. Any signature with a correct length was considered valid.

This allows an attacker to impersonate any node identity.

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.