This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate trust-dns-resolver

Dependencies

(22 total, 13 outdated, 2 insecure)

CrateRequiredLatestStatus
 backtrace^0.3.440.3.76up to date
 cfg-if^0.1.91.0.5out of date
 futures^0.3.40.3.34up to date
 ipconfig^0.2.00.3.4out of date
 lazy_static^1.01.5.0up to date
 log^0.40.4.34up to date
 lru-cache^0.1.20.1.2up to date
 resolv-conf^0.7.00.7.6up to date
 rustls ⚠️^0.170.23.45insecure
 serde^1.01.0.229up to date
 smallvec^1.21.16.1up to date
 thiserror^1.0.142.0.20out of date
 tokio ⚠️^0.2.161.53.1insecure
 tokio-openssl^0.4.00.6.5out of date
 tokio-rustls^0.130.26.5out of date
 tokio-tls^0.3.00.3.1up to date
 trust-dns-https^0.19.60.21.1out of date
 trust-dns-native-tls^0.19.60.21.1out of date
 trust-dns-openssl^0.19.60.21.1out of date
 trust-dns-proto^0.19.60.23.2out of date
 trust-dns-rustls^0.19.60.21.1out of date
 webpki-roots^0.191.0.9out of date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 env_logger^0.70.11.11out of date
 futures^0.3.40.3.34up to date

Security Vulnerabilities

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.

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.