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

Dependencies

(36 total, 10 outdated, 5 possibly insecure)

CrateRequiredLatestStatus
 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^2.2.02.6.0up to date
 enum-as-inner^0.60.6.0up to date
 futures-channel^0.3.50.3.30up to date
 futures-io^0.3.50.3.30up to date
 futures-util^0.3.50.3.30up to date
 h2 ⚠️^0.3.00.4.5out of date
 http^0.21.1.0out of date
 idna^0.4.01.0.0out of date
 ipnet^2.3.02.9.0up to date
 js-sys^0.3.440.3.69up to date
 native-tls^0.20.2.12up to date
 once_cell^1.18.01.19.0up to date
 openssl^0.10.550.10.64up to date
 quinn^0.100.11.2out of date
 rand^0.80.8.5up to date
 ring^0.160.17.8out of date
 rustls ⚠️^0.21.00.23.9out of date
 rustls-pemfile^1.0.02.1.2out of date
 serde^1.01.0.203up to date
 smallvec ⚠️^1.61.13.2maybe insecure
 socket2^0.50.5.7up to date
 thiserror^1.0.201.0.61up to date
 tinyvec^1.1.11.6.0up to date
 tokio ⚠️^1.211.38.0maybe insecure
 tokio-native-tls^0.3.00.3.1up to date
 tokio-openssl^0.6.00.6.4up to date
 tokio-rustls^0.24.00.26.0out of date
 tracing^0.1.300.1.40up to date
 url^2.4.02.5.1up to date
 wasm-bindgen^0.2.580.2.92up to date
 rustls-webpki ⚠️^0.101.00.102.4out of date
 webpki-roots^0.25.00.26.2out of date

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-executor^0.3.50.3.30up to date
 openssl^0.10.550.10.64up to date
 tokio ⚠️^1.211.38.0maybe insecure
 tracing-subscriber^0.30.3.18up to date

Security Vulnerabilities

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

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

RUSTSEC-2023-0001

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.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

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

RUSTSEC-2023-0053

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 https://github.com/briansmith/webpki/issues/69 and re-reported to us recently by Luke Malinowski.

h2: Degradation of service in h2 servers with CONTINUATION Flood

RUSTSEC-2024-0332

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 "https://seanmonstar.com/blog/hyper-http2-continuation-flood/.

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

RUSTSEC-2024-0336

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.