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 async-smtp

Dependencies

(9 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.98up to date
 async-std^1.111.13.1up to date
 base64^0.22.10.22.1up to date
 futures^0.3.210.3.31up to date
 log^0.40.4.27up to date
 nom^7.08.0.0out of date
 pin-project^11.1.10up to date
 thiserror^12.0.12out of date
 tokio ⚠️^11.44.2maybe insecure

Dev dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.111.13.1up to date
 criterion^0.30.5.1out of date
 env_logger^0.90.11.8out of date
 glob^0.30.3.2up to date
 tokio ⚠️^11.44.2maybe 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);