This project contains known security vulnerabilities. Find detailed information at the bottom.
libp2p-core(24 total, 15 outdated, 3 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| asn1_der | ^0.6.1 | 0.7.7 | out of date |
| bs58 | ^0.3.0 | 0.5.1 | out of date |
| ed25519-dalek ⚠️ | ^1.0.0-pre.3 | 3.0.0 | insecure |
| fnv | ^1.0 | 1.0.7 | up to date |
| futures | ^0.3.1 | 0.3.34 | up to date |
| futures-timer | ^3 | 3.0.4 | up to date |
| lazy_static | ^1.2 | 1.5.0 | up to date |
| libsecp256k1 ⚠️ | ^0.3.1 | 0.7.2 | insecure |
| log | ^0.4 | 0.4.34 | up to date |
| parity-multiaddr | ^0.7.2 | 0.11.2 | out of date |
| parity-multihash | ^0.2.1 | 0.2.3 | up to date |
| multistream-select | ^0.7.0 | 0.14.0 | out of date |
| parking_lot | ^0.10.0 | 0.12.5 | out of date |
| pin-project | ^0.4.6 | 1.1.13 | out of date |
| prost | ^0.6.1 | 0.14.4 | out of date |
| rand | ^0.7 | 0.10.3 | out of date |
| ring ⚠️ | ^0.16.9 | 0.17.14 | insecure |
| rw-stream-sink | ^0.2.0 | 0.5.0 | out of date |
| sha2 | ^0.8.0 | 0.11.0 | out of date |
| smallvec | ^1.0 | 1.16.2 | up to date |
| thiserror | ^1.0 | 2.0.21 | out of date |
| unsigned-varint | ^0.3 | 0.8.0 | out of date |
| void | ^1 | 1.0.2 | up to date |
| zeroize | ^1 | 1.9.0 | up to date |
(3 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-std | ^1.0 | 1.13.2 | up to date |
| quickcheck | ^0.9.0 | 1.1.0 | out of date |
| wasm-timer | ^0.2 | 0.2.5 | up to date |
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.
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.
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.