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


(23 total, 6 outdated, 3 possibly insecure)

 async-trait^0.1.430.1.80up to date
 bytes^11.6.0up to date
 cfg-if^11.0.0up to date
 drain^ to date
 enum-as-inner^ to date
 futures-executor^ to date
 futures-util^ to date
 h2 ⚠️^ of date
 http^ of date
 openssl^0.10.550.10.64up to date
 rusqlite^ of date
 rustls ⚠️^ of date
 serde^ to date
 thiserror^ to date
 time^ to date
 tokio ⚠️^ insecure
 tokio-openssl^ to date
 tokio-rustls^ of date
 toml^ of date
 tracing^0.1.300.1.40up to date
 trust-dns-proto^ to date
 trust-dns-recursor^ to date
 trust-dns-resolver^ to date

Dev dependencies

(2 total, 1 possibly insecure)

 tokio ⚠️^ insecure
 tracing-subscriber^ to date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption


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.


Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();

h2: Degradation of service in h2 servers with CONTINUATION Flood


An attacker can send a flood of CONTINUATION frames, causing h2 to process them indefinitely. This results in an increase in CPU usage.

Tokio task budget helps prevent this from a complete denial-of-service, as the server can still respond to legitimate requests, albeit with increased latency.

More details at "

Patches available for 0.4.x and 0.3.x versions.

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input


If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.