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


(36 total, 10 outdated, 5 possibly insecure)

 async-trait^0.1.430.1.80up to date
 backtrace^0.3.500.3.73up to date
 bytes^11.6.0up to date
 cfg-if^11.0.0up to date
 data-encoding^ to date
 enum-as-inner^ to date
 futures-channel^ to date
 futures-io^ to date
 futures-util^ to date
 h2 ⚠️^ of date
 http^ of date
 idna^ of date
 ipnet^ to date
 js-sys^0.3.440.3.69up to date
 native-tls^ to date
 once_cell^ to date
 openssl^0.10.550.10.64up to date
 quinn^ of date
 rand^ to date
 ring^ of date
 rustls ⚠️^ of date
 rustls-pemfile^ of date
 serde^ to date
 smallvec ⚠️^ insecure
 socket2^ to date
 thiserror^ to date
 tinyvec^ to date
 tokio ⚠️^ insecure
 tokio-native-tls^ to date
 tokio-openssl^ to date
 tokio-rustls^ of date
 tracing^0.1.300.1.40up to date
 url^ to date
 wasm-bindgen^0.2.580.2.92up to date
 rustls-webpki ⚠️^ of date
 webpki-roots^ of date

Dev dependencies

(4 total, 1 possibly insecure)

 futures-executor^ to date
 openssl^0.10.550.10.64up to date
 tokio ⚠️^ insecure
 tracing-subscriber^ to date

Security Vulnerabilities

smallvec: Buffer overflow in SmallVec::insert_many


A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.

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.

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.