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 dill-impl

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 proc-macro2^11.0.106up to date
 syn^22.0.114up to date
 quote^11.0.44up to date

Crate dill

Dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 indoc^22.0.7up to date
 thiserror^22.0.18up to date
 multimap^0.100.10.1up to date
 tokio ⚠️^11.49.0maybe insecure

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 pretty_assertions^11.4.1up to date
 tokio ⚠️^11.49.0maybe insecure

Crate example-axum

Dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 axum^0.80.8.8up to date
 axum-extra^0.120.12.5up to date
 headers^0.40.4.1up to date
 http^11.4.0up to date
 tokio ⚠️^11.49.0maybe insecure
 tower^0.50.5.3up to date

Crate example-cli

Dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.89up to date
 clap^44.5.54up to date
 tokio ⚠️^11.49.0maybe 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);