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

(14 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.83up to date
 bollard^0.110.17.1out of date
 bollard-stubs^1.411.41.0up to date
 conquer-once ⚠️^0.30.4.0out of date
 futures^0.30.3.31up to date
 hex^0.40.4.3up to date
 hmac^0.120.12.1up to date
 log^0.40.4.22up to date
 rand^0.80.8.5up to date
 serde^11.0.210up to date
 serde_json^11.0.128up to date
 sha2^0.100.10.8up to date
 signal-hook^0.30.3.17up to date
 tokio ⚠️^11.40.0maybe insecure

Dev dependencies

(19 total, 14 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bitcoincore-rpc^0.150.19.0out of date
 json^0.120.12.4up to date
 lapin^1.8.02.5.0out of date
 mongodb^2.1.03.1.0out of date
 orientdb-client^0.60.6.0up to date
 postgres^0.190.19.9up to date
 pretty_env_logger^0.40.5.0out of date
 rdkafka^0.280.36.2out of date
 redis^0.210.27.4out of date
 reqwest^0.110.12.8out of date
 rusoto_core^0.470.48.0out of date
 rusoto_credential^0.470.48.0out of date
 rusoto_dynamodb^0.470.48.0out of date
 rusoto_s3^0.470.48.0out of date
 rusoto_sqs^0.470.48.0out of date
 spectral^0.60.6.0up to date
 tokio ⚠️^11.40.0maybe insecure
 tokio-amqp^1.0.02.0.0out of date
 zookeeper^0.60.8.0out of date

Security Vulnerabilities

conquer-once: conquer-once's OnceCell lacks Send bound for its Sync trait.

RUSTSEC-2020-0101

Affected versions of conquer-once implements Sync for its OnceCell type without restricting it to Sendable types.

This allows non-Send but Sync types such as MutexGuard to be sent across threads leading to undefined behavior and memory corruption in concurrent programs.

The issue was fixed by adding a Send constraint to OnceCell.

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