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 thirtyfour

Dependencies

(18 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.89up to date
 base64^0.220.22.1up to date
 futures^0.30.3.31up to date
 http^11.3.1up to date
 indexmap^2.12.11.3up to date
 parking_lot^0.120.12.4up to date
 paste^11.0.15up to date
 reqwest^0.120.12.23up to date
 serde^1.0.1111.0.225up to date
 serde_json^11.0.145up to date
 serde_repr^0.1.180.1.20up to date
 stringmatch^0.40.4.0up to date
 strum^0.260.27.2out of date
 thirtyfour-macros^0.1.10.2.0out of date
 thiserror^12.0.16out of date
 tokio ⚠️^11.47.1maybe insecure
 tracing^0.10.1.41up to date
 url^2.52.5.7up to date

Dev dependencies

(6 total, 3 outdated)

CrateRequiredLatestStatus
 assert_matches^1.51.5.0up to date
 axum^0.70.8.4out of date
 color-eyre^0.60.6.5up to date
 rstest^0.180.26.1out of date
 tower-http^0.50.6.6out of date
 tracing-subscriber^0.30.3.20up 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);