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


(17 total, 3 outdated, 3 possibly insecure)

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

Dev dependencies

(4 total, 2 possibly insecure)

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

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read


When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.

webpki: 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.

This was previously reported in and re-reported recently by Luke Malinowski.

webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.