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


(14 total, 2 outdated, 3 possibly insecure)

 cfg-if^11.0.0up to date
 data-encoding^ to date
 futures-channel^ to date
 futures-util^ to date
 once_cell^ to date
 radix_trie^ to date
 rand^ to date
 rustls ⚠️^ of date
 serde^ to date
 thiserror^ to date
 tokio ⚠️^ insecure
 tracing^0.1.300.1.40up to date
 trust-dns-proto^ to date
 rustls-webpki ⚠️^ of date

Dev dependencies

(4 total, 1 possibly insecure)

 futures^ to date
 openssl^0.10.550.10.64up to date
 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();

rustls-webpki: rustls-webpki: CPU denial of service in certificate path building


When this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.

Both TLS clients and TLS servers that accept client certificate are affected.

We now give each path building operation a budget of 100 signature verifications.

The original webpki crate is also affected.

This was previously reported in the original crate and re-reported to us recently by Luke Malinowski.

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.