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 hickory-resolver

Dependencies

(22 total, 3 possibly insecure)

CrateRequiredLatestStatus
 backtrace^0.3.500.3.74up to date
 cfg-if^11.0.0up to date
 futures-util^0.3.50.3.31up to date
 hickory-proto^0.25.0-alpha.40.24.2up to date
 ipconfig^0.3.00.3.2up to date
 moka^0.120.12.8up to date
 once_cell^1.20.01.20.2up to date
 parking_lot^0.120.12.3up to date
 quinn^0.11.20.11.6up to date
 rand^0.80.8.5up to date
 resolv-conf^0.7.00.7.0up to date
 rustls ⚠️^0.23.140.23.20maybe insecure
 rustls-native-certs^0.80.8.1up to date
 serde^1.01.0.216up to date
 smallvec ⚠️^1.61.13.2maybe insecure
 thiserror^22.0.7up to date
 tokio ⚠️^1.211.42.0maybe insecure
 tokio-native-tls^0.3.00.3.1up to date
 tokio-openssl^0.6.00.6.5up to date
 tokio-rustls^0.260.26.1up to date
 tracing^0.1.300.1.41up to date
 webpki-roots^0.260.26.7up to date

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-executor^0.3.50.3.31up to date
 tokio ⚠️^1.211.42.0maybe insecure
 toml^0.8.140.8.19up to date
 tracing-subscriber^0.30.3.19up 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: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.