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 testcontainers

Dependencies

(25 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.83up to date
 bollard^0.17.00.18.1out of date
 bollard-stubs=1.45.0-rc.26.0.11.41.0up to date
 bytes^1.6.01.9.0up to date
 conquer-once^0.40.4.0up to date
 docker_credential^1.3.11.3.1up to date
 either^1.12.01.13.0up to date
 etcetera^0.8.00.8.0up to date
 futures^0.30.3.31up to date
 log^0.40.4.22up to date
 memchr^2.7.22.7.4up to date
 parse-display^0.9.00.10.0out of date
 pin-project-lite^0.2.140.2.15up to date
 reqwest^0.12.50.12.9up to date
 serde^11.0.216up to date
 serde-java-properties^0.2.00.2.0up to date
 serde_json^11.0.133up to date
 serde_with^3.7.03.11.0up to date
 signal-hook^0.30.3.17up to date
 thiserror^1.0.602.0.7out of date
 tokio ⚠️^11.42.0maybe insecure
 tokio-stream^0.1.150.1.17up to date
 tokio-tar^0.3.10.3.1up to date
 tokio-util^0.7.100.7.13up to date
 url^22.5.4up to date

Dev dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.861.0.94up to date
 pretty_env_logger^0.50.5.0up to date
 reqwest^0.12.40.12.9up to date
 temp-dir^0.1.130.1.14up to date
 tokio ⚠️^11.42.0maybe 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);