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

Dependencies

(23 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.430.1.63up to date
 bytes^11.3.0up to date
 cfg-if^11.0.0up to date
 enum-as-inner^0.50.5.1up to date
 futures-executor^0.3.50.3.25up to date
 futures-util^0.3.50.3.25up to date
 h2^0.3.00.3.15up to date
 http^0.20.2.8up to date
 openssl ⚠️^0.100.10.45maybe insecure
 rusqlite^0.28.00.28.0up to date
 rustls^0.200.20.8up to date
 serde^1.0.1141.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
 tokio-openssl^0.6.00.6.3up to date
 tokio-rustls^0.23.00.23.4up to date
 toml^0.50.7.0out of date
 tracing^0.1.300.1.37up to date
 trust-dns-client^0.22.00.22.0up to date
 trust-dns-proto^0.22.00.22.0up to date
 trust-dns-recursor^0.22.00.22.0up to date
 trust-dns-resolver^0.22.00.22.0up to date

Dev dependencies

(2 total, 1 possibly insecure)

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