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.220.22.1up to date
 http-body-util^0.10.1.3up to date
 hyper^1.11.6.0up to date
 hyper-rustls^0.270.27.5up to date
 hyper-util^0.10.1.11up to date
 indexmap^2.62.9.0up to date
 ipnet^22.11.0up to date
 metrics^0.240.24.2up to date
 metrics-util^0.190.19.1up to date
 quanta^0.120.12.5up to date
 thiserror^22.0.12up to date
 tokio ⚠️^11.44.2maybe insecure
 tracing^0.10.1.41up to date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 proptest^11.6.0up to date
 rand^0.90.9.1up to date
 tracing^0.10.1.41up to date
 tracing-subscriber^0.30.3.19up 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);