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 scuffle-bootstrap-telemetry

Dependencies

(19 total, 9 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.100up to date
 bytes^11.11.0up to date
 http^11.4.0up to date
 http-body^11.0.1up to date
 http-body-util^0.1.20.1.3up to date
 opentelemetry^0.270.31.0out of date
 opentelemetry-appender-tracing^0.270.31.1out of date
 opentelemetry_sdk^0.270.31.0out of date
 prometheus-client^0.22.30.24.0out of date
 querystring^11.1.0up to date
 scuffle-bootstrap^0.0.20.1.7out of date
 scuffle-context^0.0.20.1.5out of date
 scuffle-http^0.0.40.3.2out of date
 scuffle-pprof^0.0.20.2.0out of date
 scuffle-workspace-hack^0.1.00.1.0up to date
 thiserror^22.0.17up to date
 tokio ⚠️^11.48.0maybe insecure
 tracing^0.10.1.43up to date
 tracing-opentelemetry^0.28.00.32.0out of 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);