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-quic(17 total, 5 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-std | ^1.12.0 | 1.13.2 | up to date |
| bytes | ^1.6.0 | 1.11.0 | up to date |
| futures | ^0.3.30 | 0.3.31 | up to date |
| futures-timer | ^3.0.3 | 3.0.3 | up to date |
| if-watch | ^3.2.0 | 3.2.1 | up to date |
| libp2p-core | ^0.41.2 | 0.43.1 | out of date |
| libp2p-identity | ^0.2.8 | 0.2.13 | up to date |
| libp2p-tls | ^0.4.0 | 0.6.2 | out of date |
| parking_lot | ^0.12.2 | 0.12.5 | up to date |
| quinn | ^0.11.0 | 0.11.9 | up to date |
| rand | ^0.8.5 | 0.9.2 | out of date |
| ring ⚠️ | ^0.17.8 | 0.17.14 | maybe insecure |
| rustls ⚠️ | ^0.23.5 | 0.23.35 | maybe insecure |
| socket2 | ^0.5.7 | 0.6.1 | out of date |
| thiserror | ^1.0.61 | 2.0.17 | out of date |
| tokio | ^1.37 | 1.48.0 | up to date |
| tracing | ^0.1.37 | 0.1.43 | up to date |
(8 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-std | ^1.12.0 | 1.13.2 | up to date |
| libp2p-identity | ^0.2.8 | 0.2.13 | up to date |
| libp2p-noise | ^0.44.0 | 0.46.1 | out of date |
| libp2p-tcp | ^0.41.0 | 0.44.0 | out of date |
| libp2p-yamux | ^0.45.1 | 0.47.0 | out of date |
| quickcheck | ^1 | 1.0.3 | up to date |
| tokio | ^1.37 | 1.48.0 | up to date |
| tracing-subscriber ⚠️ | ^0.3 | 0.3.22 | maybe insecure |
rustls: rustls network-reachable panic in `Acceptor::accept`A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept() are affected.
Servers that use tokio-rustls's LazyConfigAcceptor API are affected.
Servers that use tokio-rustls's TlsAcceptor API are not affected.
Servers that use rustls-ffi's rustls_acceptor_accept API are affected.
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.
tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequencesPrevious versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:
In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.
This was patched in PR #3368 to escape ANSI control characters from user input.