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 mailbridge

Dependencies

(17 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.102up to date
 async-trait^0.10.1.89up to date
 base64^0.220.22.1up to date
 dotenvy^0.150.15.7up to date
 governor^0.100.10.4up to date
 lettre^0.110.11.22up to date
 reqwest^0.130.13.4up to date
 scylla^11.7.0up to date
 secrecy^0.100.10.3up to date
 serde^11.0.228up to date
 serde_json^11.0.150up to date
 sqlx^0.90.9.0up to date
 thiserror^22.0.18up to date
 tokio ⚠️^11.52.3maybe insecure
 tracing^0.10.1.44up to date
 url^22.5.8up to date
 uuid^11.23.3up to date

Dev dependencies

(1 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^11.52.3maybe 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);