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-core(28 total, 21 outdated, 5 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| asn1_der ⚠️ | ^0.6.1 | 0.7.6 | out of date |
| bs58 | ^0.2.0 | 0.5.1 | out of date |
| bytes | ^0.4 | 1.6.0 | out of date |
| ed25519-dalek ⚠️ | ^1.0.0-pre.1 | 2.1.1 | out of date |
| failure | ^0.1 | 0.1.8 | up to date |
| fnv | ^1.0 | 1.0.7 | up to date |
| futures | ^0.1 | 0.3.30 | out of date |
| lazy_static | ^1.2 | 1.4.0 | up to date |
| libsecp256k1 ⚠️ | ^0.2.2 | 0.7.1 | out of date |
| log | ^0.4 | 0.4.21 | up to date |
| parity-multiaddr | ^0.5.0 | 0.11.2 | out of date |
| parity-multihash | ^0.1.0 | 0.2.3 | out of date |
| multistream-select | ^0.4.0 | 0.13.0 | out of date |
| parking_lot | ^0.8 | 0.12.1 | out of date |
| protobuf ⚠️ | ^2.3 | 3.4.0 | out of date |
| quick-error | ^1.2 | 2.0.1 | out of date |
| rand | ^0.6 | 0.8.5 | out of date |
| ring | ^0.14 | 0.17.8 | out of date |
| rw-stream-sink | ^0.1.1 | 0.4.0 | out of date |
| sha2 | ^0.8.0 | 0.10.8 | out of date |
| smallvec ⚠️ | ^0.6 | 1.13.2 | out of date |
| tokio-executor | ^0.1.4 | 0.1.10 | up to date |
| tokio-io | ^0.1 | 0.1.13 | up to date |
| unsigned-varint | ^0.2 | 0.8.0 | out of date |
| untrusted | ^0.6 | 0.9.0 | out of date |
| void | ^1 | 1.0.2 | up to date |
| wasm-timer | ^0.1 | 0.2.5 | out of date |
| zeroize | ^0.9 | 1.7.0 | out of date |
(8 total, 5 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| assert_matches | ^1.3 | 1.5.0 | up to date |
| env_logger | ^0.6 | 0.11.3 | out of date |
| quickcheck | ^0.8 | 1.0.3 | out of date |
| rand | ^0.6 | 0.8.5 | out of date |
| tokio ⚠️ | ^0.1 | 1.37.0 | out of date |
| tokio-codec | ^0.1 | 0.1.2 | up to date |
| tokio-mock-task | ^0.1 | 0.1.1 | up to date |
| wasm-timer | ^0.1 | 0.2.5 | 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.
asn1_der: Processing of maliciously crafted length fields causes memory allocation SIGABRTsAffected versions of this crate tried to preallocate a vector for an arbitrary amount of bytes announced by the ASN.1-DER length field without further checks.
This allows an attacker to trigger a SIGABRT by creating length fields that announce more bytes than the allocator can provide.
The flaw was corrected by not preallocating memory.
libsecp256k1: Flaw in Scalar::check_overflow allows side-channel timing attackVersions of libsecp256k1 prior to 0.3.1 did not execute
Scalar::check_overflow in constant time.
This allows an attacker to potentially leak information via a timing attack.
The flaw was corrected by modifying Scalar::check_overflow to execute in constant time.
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.
libsecp256k1: libsecp256k1 allows overflowing signatureslibsecp256k1 accepts signatures whose R or S parameter is larger than the secp256k1 curve order, which differs from other implementations. This could lead to invalid signatures being verified.
The error is resolved in 0.5.0 by adding a check_overflow flag.
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 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.
ed25519-dalek: Double Public Key Signing Function Oracle Attack on `ed25519-dalek`Versions of ed25519-dalek prior to v2.0 model private and public keys as
separate types which can be assembled into a Keypair, and also provide APIs
for serializing and deserializing 64-byte private/public keypairs.
Such APIs and serializations are inherently unsafe as the public key is one of
the inputs used in the deterministic computation of the S part of the signature,
but not in the R value. An adversary could somehow use the signing function as
an oracle that allows arbitrary public keys as input can obtain two signatures
for the same message sharing the same R and only differ on the S part.
Unfortunately, when this happens, one can easily extract the private key.
Revised public APIs in v2.0 of ed25519-dalek do NOT allow a decoupled
private/public keypair as signing input, except as part of specially labeled
"hazmat" APIs which are clearly labeled as being dangerous if misused.