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

(16 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-recursion^1.0.01.1.1up to date
 async-trait^0.1.430.1.83up to date
 bytes^11.7.2up to date
 cfg-if^11.0.0up to date
 enum-as-inner^0.60.6.1up to date
 futures-executor^0.3.50.3.31up to date
 futures-util^0.3.50.3.31up to date
 lru-cache^0.1.20.1.2up to date
 parking_lot^0.120.12.3up to date
 serde^1.01.0.210up to date
 thiserror^1.0.201.0.64up to date
 tokio ⚠️^1.211.40.0maybe insecure
 toml^0.70.8.19out of date
 tracing^0.1.300.1.40up to date
 trust-dns-proto^0.23.20.23.2up to date
 trust-dns-resolver^0.23.20.23.2up to date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.211.40.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);