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-client

Dependencies

(17 total, 2 possibly insecure)

CrateRequiredLatestStatus
 cfg-if^11.0.0up to date
 data-encoding^2.2.02.3.3up to date
 futures-channel^0.3.50.3.25up to date
 futures-util^0.3.50.3.25up to date
 lazy_static^1.2.01.4.0up to date
 openssl ⚠️^0.100.10.45maybe insecure
 radix_trie^0.2.00.2.1up to date
 rand^0.80.8.5up to date
 ring^0.160.16.20up to date
 rustls^0.20.00.20.8up to date
 serde^1.01.0.152up to date
 thiserror^1.0.201.0.38up to date
 time^0.30.3.17up to date
 tokio ⚠️^1.01.24.2maybe insecure
 tracing^0.1.300.1.37up to date
 trust-dns-proto^0.22.00.22.0up to date
 webpki^0.22.00.22.0up to date

Dev dependencies

(4 total, 2 possibly insecure)

CrateRequiredLatestStatus
 futures^0.3.50.3.25up to date
 openssl ⚠️^0.100.10.45maybe insecure
 tokio ⚠️^1.01.24.2maybe insecure
 tracing-subscriber^0.30.3.16up to date

Security Vulnerabilities

openssl: Use after free in CMS Signing

RUSTSEC-2018-0010

Affected versions of the OpenSSL crate used structures after they'd been freed.

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 overriden 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);