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 mcap

Dependencies

(13 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bimap^0.6.30.6.3up to date
 binrw^0.12.00.15.0out of date
 byteorder^1.41.5.0up to date
 crc32fast^1.31.5.0up to date
 enumset^1.0.111.1.10up to date
 log^0.40.4.28up to date
 lz4^1.271.28.1up to date
 num_cpus^1.131.17.0up to date
 paste^1.01.0.15up to date
 static_assertions^1.1.01.1.0up to date
 thiserror^1.02.0.17out of date
 tokio ⚠️^11.47.1maybe insecure
 zstd^0.130.13.3up to date

Dev dependencies

(14 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.100up to date
 assert_matches^1.5.01.5.0up to date
 atty^0.20.2.14up to date
 camino^1.01.2.1up to date
 clap^3.24.5.48out of date
 criterion^0.5.10.7.0out of date
 itertools^0.100.14.0out of date
 memmap2^0.9.50.9.8up to date
 rayon^1.51.11.0up to date
 serde^1.0.1451.0.228up to date
 serde_json^11.0.145up to date
 simplelog^0.120.12.2up to date
 tempfile^3.33.23.0up to date
 tokio ⚠️^11.47.1maybe insecure

Security Vulnerabilities

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