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-secio(23 total, 16 outdated, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| aes-ctr | ^0.3 | 0.99.99 | out of date |
| aesni | ^0.6 | 0.99.99 | out of date |
| asn1_der ⚠️ | ^0.6.1 | 0.7.6 | out of date |
| bytes | ^0.4 | 1.10.1 | out of date |
| ctr | ^0.3 | 0.9.2 | out of date |
| futures | ^0.1 | 0.3.31 | out of date |
| hmac | ^0.7.0 | 0.12.1 | out of date |
| js-sys | ^0.3.10 | 0.3.77 | up to date |
| lazy_static | ^1.2.0 | 1.5.0 | up to date |
| libp2p-core ⚠️ | ^0.8.0 | 0.43.1 | out of date |
| log | ^0.4.6 | 0.4.27 | up to date |
| parity-send-wrapper | ^0.1 | 0.1.0 | up to date |
| protobuf ⚠️ | ^2.3 | 3.7.2 | out of date |
| rand | ^0.6.5 | 0.9.1 | out of date |
| ring ⚠️ | ^0.14 | 0.17.14 | out of date |
| rw-stream-sink | ^0.1.1 | 0.4.0 | out of date |
| sha2 | ^0.8.0 | 0.10.9 | out of date |
| tokio-io | ^0.1.0 | 0.1.13 | up to date |
| twofish | ^0.2.0 | 0.7.1 | out of date |
| untrusted | ^0.6 | 0.9.0 | out of date |
| wasm-bindgen | ^0.2.33 | 0.2.100 | up to date |
| wasm-bindgen-futures | ^0.3.10 | 0.4.50 | out of date |
| web-sys | ^0.3.10 | 0.3.77 | up to date |
(4 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.2 | 0.6.0 | out of date |
| libp2p-tcp | ^0.8.0 | 0.44.0 | out of date |
| tokio ⚠️ | ^0.1 | 1.46.1 | out of date |
| tokio-tcp | ^0.1 | 0.1.4 | up to date |
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.
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.
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.
protobuf: Crash due to uncontrolled recursion in protobuf crateAffected version of this crate did not properly parse unknown fields when parsing a user-supplied input.
This allows an attacker to cause a stack overflow when parsing the mssage on untrusted data.
ring: Some AES functions may panic when overflow checking is enabled.ring::aead::quic::HeaderProtectionKey::new_mask() may panic when overflow
checking is enabled. In the QUIC protocol, an attacker can induce this panic by
sending a specially-crafted packet. Even unintentionally it is likely to occur
in 1 out of every 2**32 packets sent and/or received.
On 64-bit targets operations using ring::aead::{AES_128_GCM, AES_256_GCM} may
panic when overflow checking is enabled, when encrypting/decrypting approximately
68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols
like TLS and SSH are not affected by this because those protocols break large
amounts of data into small chunks. Similarly, most applications will not
attempt to encrypt/decrypt 64GB of data in one chunk.
Overflow checking is not enabled in release mode by default, but
RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml
profile can override this. Overflow checking is usually enabled by default in
debug mode.