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-prometheus

Dependencies

(15 total, 9 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 axum^0.6.10.7.7out of date
 axum-core^0.3.00.4.5out of date
 bytes^1.2.11.8.0up to date
 futures^0.3.230.3.31up to date
 futures-core^0.3.240.3.31up to date
 http^0.2.81.1.0out of date
 http-body^0.4.51.0.1out of date
 matchit^0.70.8.4out of date
 metrics^0.21.00.24.0out of date
 metrics-exporter-prometheus^0.12.00.16.0out of date
 once_cell^1.17.01.20.2up to date
 pin-project^1.0.121.1.7up to date
 tokio ⚠️^1.20.11.41.0maybe insecure
 tower^0.4.130.5.1out of date
 tower-http^0.4.00.6.1out of date

Dev dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 hyper^0.14.201.5.0out of date
 insta^1.31.01.41.0up to date
 tower-service^0.3.20.3.3up 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);