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 tor-rtcompat

Dependencies

(26 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arbitrary^1.3.21.4.2up to date
 async-io^2.2.12.6.0up to date
 async-native-tls^0.5.00.6.0out of date
 async-std^1.7.01.13.2up to date
 async-trait^0.1.540.1.89up to date
 async_executors^0.7.00.7.0up to date
 asynchronous-codec^0.7.00.7.0up to date
 coarsetime^0.1.200.1.37up to date
 derive_more^2.0.12.1.1up to date
 dyn-clone^1.0.171.0.20up to date
 educe^0.4.60.6.0out of date
 futures^0.3.140.3.32up to date
 futures-rustls^0.26.00.26.0up to date
 libc^0.20.2.182up to date
 native-tls^0.20.2.18up to date
 paste^11.0.15up to date
 pin-project^11.1.10up to date
 rustls-pki-types^11.14.0up to date
 thiserror^22.0.18up to date
 tokio ⚠️^1.71.49.0maybe insecure
 tokio-util^0.7.00.7.18up to date
 tor-error^0.28.00.39.0out of date
 tor-general-addr^0.28.00.39.0out of date
 tracing^0.1.360.1.44up to date
 void^11.0.2up to date
 x509-signature^0.5.00.5.0up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 assert_matches^1.5.01.5.0up to date
 native-tls^0.20.2.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);