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

Dependencies

(13 total, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.22.00.22.1up to date
 http-body-util^0.1.00.1.1up to date
 hyper^1.11.3.1up to date
 hyper-tls^0.6.00.6.0up to date
 hyper-util^0.1.30.1.3up to date
 indexmap^2.12.2.6up to date
 ipnet^22.9.0up to date
 metrics^0.220.22.3up to date
 metrics-util^0.160.16.3up to date
 quanta^0.120.12.3up to date
 thiserror^11.0.59up to date
 tokio ⚠️^11.37.0maybe insecure
 tracing^0.1.260.1.40up to date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 proptest^11.4.0up to date
 rand^0.80.8.5up to date
 tracing^0.10.1.40up to date
 tracing-subscriber^0.30.3.18up 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);