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, 9 outdated, 3 possibly insecure)

 async-trait^0.1.430.1.73up to date
 bytes^11.5.0up to date
 cfg-if^11.0.0up to date
 enum-as-inner^ of date
 futures-executor^ to date
 futures-util^ to date
 h2 ⚠️^ insecure
 http^ to date
 openssl ⚠️^ insecure
 rusqlite^ of date
 rustls^ of date
 serde^1.0.1141.0.188up 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.37up to date
 trust-dns-client^ of date
 trust-dns-proto^ of date
 trust-dns-recursor^ of date
 trust-dns-resolver^ of 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: Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS)


If an attacker is able to flood the network with pairs of HEADERS/RST_STREAM frames, such that the h2 application is not able to accept them faster than the bytes are received, the pending accept queue can grow in memory usage. Being able to do this consistently can result in excessive memory use, and eventually trigger Out Of Memory.

This flaw is corrected in hyperium/h2#668, which restricts remote reset stream count by default.

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.