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.

Crate libp2p-rendezvous

Dependencies

(14 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 asynchronous-codec^0.60.7.0out of date
 bimap^0.6.10.6.3up to date
 futures^0.30.3.31up to date
 futures-timer^3.0.23.0.3up to date
 instant^0.1.110.1.13up to date
 libp2p-core ⚠️^0.31.00.42.0out of date
 libp2p-swarm^0.33.00.45.1out of date
 log^0.40.4.22up to date
 prost^0.90.13.3out of date
 rand^0.80.8.5up to date
 sha2^0.100.10.8up to date
 thiserror^11.0.68up to date
 unsigned-varint^0.70.8.0out of date
 void^11.0.2up to date

Dev dependencies

(4 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.83up to date
 env_logger^0.80.11.5out of date
 rand^0.80.8.5up to date
 tokio ⚠️^1.151.41.0maybe insecure

Security Vulnerabilities

libp2p-core: Failure to verify the public key of a `SignedEnvelope` against the `PeerId` in a `PeerRecord`

RUSTSEC-2022-0009

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 corruption

RUSTSEC-2023-0001

On 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.

Workarounds

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);