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 amqp-service

Dependencies

(13 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.17.01.45.0maybe insecure
 futures^0.3.210.3.31up to date
 tracing-subscriber^0.3.110.3.19up to date
 actix-web^44.11.0up to date
 futures-lite^1.12.02.6.0out of date
 lapin^2.1.12.5.3up to date
 bb8^0.8.00.9.0out of date
 bb8-lapin^0.4.00.6.0out of date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 log^0.4.160.4.27up to date
 reqwest^0.11.100.12.15out of date
 num_cpus^1.13.11.16.0up 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);