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 axum-sessions

Dependencies

(8 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-session^3.0.03.0.0up to date
 axum^0.6.00.7.9out of date
 axum-extra^0.7.10.9.6out of date
 futures^0.3.210.3.31up to date
 http-body^0.4.51.0.1out of date
 tokio ⚠️^1.20.11.41.1maybe insecure
 tower^0.4.120.5.1out of date
 tracing^0.10.1.40up to date

Dev dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 http^0.2.81.1.0out of date
 hyper^0.14.191.5.1out of date
 rand^0.8.50.8.5up to date
 serde^1.0.1471.0.215up to date
 tokio ⚠️^1.20.11.41.1maybe 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);