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 multer

Dependencies

(13 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.01.7.2up to date
 encoding_rs^0.8.200.8.34up to date
 futures-util^0.30.3.31up to date
 http^1.01.1.0up to date
 httparse^1.31.9.5up to date
 log^0.4.150.4.22up to date
 memchr^2.42.7.4up to date
 mime^0.3.100.3.17up to date
 serde^1.01.0.210up to date
 serde_json^1.01.0.128up to date
 spin^0.90.9.8up to date
 tokio ⚠️^1.01.40.0maybe insecure
 tokio-util^0.70.7.12up to date

Dev dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 http-body-util^0.10.1.2up to date
 hyper^1.01.4.1up to date
 hyper-util^0.1.10.1.9up to date
 serde^1.01.0.210up to date
 tokio ⚠️^1.01.40.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);