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 trust-dns-recursor

Dependencies

(17 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-recursion^1.0.01.1.1up to date
 async-trait^0.1.430.1.80up to date
 bytes^11.6.0up to date
 cfg-if^11.0.0up to date
 enum-as-inner^0.50.6.0out of date
 futures-executor^0.3.50.3.30up to date
 futures-util^0.3.50.3.30up to date
 lru-cache^0.1.20.1.2up to date
 parking_lot^0.120.12.3up to date
 serde^1.0.1141.0.203up to date
 thiserror^1.0.201.0.61up to date
 time^0.30.3.36up to date
 tokio ⚠️^1.01.37.0maybe insecure
 toml^0.50.8.13out of date
 tracing^0.1.300.1.40up to date
 trust-dns-proto^0.22.00.23.2out of date
 trust-dns-resolver^0.22.00.23.2out of date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.01.37.0maybe insecure
 tracing-subscriber^0.30.3.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);