Affected versions of this crate called Vec::reserve() on user-supplied input.
This allows an attacker to cause an Out of Memory condition while calling the vulnerable method on untrusted data.
libp2p-identify 0.8.0
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.
libp2p-identify
(14 total, 9 outdated, 3 possibly insecure)
Crate | Required | Latest | Status |
---|---|---|---|
bytes | ^0.4 | 1.6.0 | out of date |
fnv | ^1 | 1.0.7 | up to date |
futures | ^0.1 | 0.3.30 | out of date |
libp2p-core ⚠️ | ^0.8.0 | 0.41.2 | out of date |
log | ^0.4.1 | 0.4.21 | up to date |
parity-multiaddr | ^0.4.0 | 0.11.2 | out of date |
parking_lot | ^0.7 | 0.12.2 | out of date |
protobuf ⚠️ | ^2.3 | 3.4.0 | out of date |
smallvec ⚠️ | ^0.6 | 1.13.2 | out of date |
tokio-codec | ^0.1 | 0.1.2 | up to date |
tokio-io | ^0.1.0 | 0.1.13 | up to date |
unsigned-varint | ^0.2.1 | 0.8.0 | out of date |
void | ^1.0 | 1.0.2 | up to date |
wasm-timer | ^0.1 | 0.2.5 | out of date |
(5 total, 5 outdated, 1 possibly insecure)
Crate | Required | Latest | Status |
---|---|---|---|
libp2p-mplex | ^0.8.0 | 0.41.0 | out of date |
libp2p-secio | ^0.8.0 | 0.26.0 | out of date |
libp2p-tcp | ^0.8.0 | 0.41.0 | out of date |
rand | ^0.6 | 0.8.5 | out of date |
tokio ⚠️ | ^0.1 | 1.37.0 | out of date |
protobuf
: Out of Memory in stream::read_raw_bytes_into()Affected versions of this crate called Vec::reserve() on user-supplied input.
This allows an attacker to cause an Out of Memory condition while calling the vulnerable method on untrusted data.
libp2p-core
: Failure to properly verify ed25519 signatures makes any signature validAffected 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.
smallvec
: Buffer overflow in SmallVec::insert_manyA bug in the SmallVec::insert_many
method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.
This bug was only triggered if the iterator passed to insert_many
yielded more items than the lower bound returned from its size_hint
method.
The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many
to use less unsafe code, so it is easier to verify its correctness.
Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.
tokio
: Data race when sending and receiving after closing a `oneshot` channelIf 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 await
ed 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 await
ed and try_recv
is not called after calling close
,
is not affected.
See tokio#4225 for more details.