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 dockertest

Dependencies

(14 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.581.0.93up to date
 async-trait^0.1.560.1.83up to date
 base64^0.13.00.22.1out of date
 bollard^0.13.00.17.1out of date
 dyn-clone^1.0.61.0.17up to date
 futures^0.3.210.3.31up to date
 lazy_static^1.4.01.5.0up to date
 rand^0.8.50.8.5up to date
 secrecy^0.8.00.10.3out of date
 serde^1.0.1371.0.215up to date
 serde_json^1.0.811.0.132up to date
 thiserror^1.0.312.0.3out of date
 tokio ⚠️^1.19.21.41.1maybe insecure
 tracing^0.1.350.1.40up to date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 access-queue^1.1.01.1.0up to date
 once_cell^1.12.01.20.2up to date
 test-log^0.2.100.2.16up to date
 tracing-subscriber^0.3.110.3.18up to date

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