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-tcp(11 total, 5 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-io | ^1.2.0 | 2.3.2 | out of date |
| futures | ^0.3.8 | 0.3.30 | up to date |
| futures-timer | ^3.0 | 3.0.3 | up to date |
| if-addrs | ^0.6.4 | 0.12.0 | out of date |
| if-watch | ^0.2.0 | 3.2.0 | out of date |
| ipnet | ^2.0.0 | 2.9.0 | up to date |
| libc | ^0.2.80 | 0.2.154 | up to date |
| libp2p-core ⚠️ | ^0.30.0 | 0.41.2 | out of date |
| log | ^0.4.11 | 0.4.21 | up to date |
| socket2 | ^0.4.0 | 0.5.7 | out of date |
| tokio ⚠️ | ^1.0.1 | 1.37.0 | maybe insecure |
(3 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-std | ^1.6.5 | 1.12.0 | up to date |
| env_logger | ^0.9.0 | 0.11.3 | out of date |
| tokio ⚠️ | ^1.0.1 | 1.37.0 | maybe insecure |
libp2p-core: Failure to verify the public key of a `SignedEnvelope` against the `PeerId` in a `PeerRecord`Affected versions of this crate did not check that the public key the signature was created with matches the peer ID of the peer record. Any combination was considered valid.
This allows an attacker to republish an existing PeerRecord with a different PeerId.
tokio: reject_remote_clients Configuration corruptionOn Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.
This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.
The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.
Ensure that pipe_mode is set first after initializing a ServerOptions. For example:
let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);