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

 async-trait^0.1.430.1.73up to date
 backtrace^0.3.500.3.69up to date
 bytes^11.5.0up to date
 cfg-if^11.0.0up to date
 data-encoding^ to date
 enum-as-inner^ of date
 futures-channel^ to date
 futures-io^ to date
 futures-util^ to date
 h2 ⚠️^ insecure
 http^ to date
 idna^ of date
 ipnet^ to date
 js-sys^0.3.440.3.64up to date
 lazy_static^ to date
 native-tls^ to date
 openssl ⚠️^ insecure
 quinn^ of date
 rand^ to date
 ring^ to date
 rustls^ of date
 rustls-pemfile^ to date
 serde^ to date
 smallvec ⚠️^ insecure
 socket2^ of 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.37up to date
 url^ to date
 wasm-bindgen^0.2.580.2.87up to date
 webpki ⚠️^ insecure
 webpki-roots^ of date

Dev dependencies

(4 total, 2 possibly insecure)

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

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.

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.