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

Crate trust-dns-client


(18 total, 2 outdated, 1 insecure, 2 possibly insecure)

 cfg-if^11.0.0up to date
 chrono ⚠️^
 data-encoding^ to date
 futures-channel^ to date
 futures-util^ to date
 lazy_static^ to date
 log^ to date
 openssl ⚠️^ insecure
 radix_trie^ to date
 rand^ to date
 ring^ to date
 rustls^ of date
 serde^ to date
 thiserror^ to date
 tokio ⚠️^ insecure
 trust-dns-https^ to date
 trust-dns-proto^ to date
 webpki^ of date

Dev dependencies

(2 total, 1 possibly insecure)

 futures^ to date
 openssl ⚠️^ insecure

Security Vulnerabilities

openssl: Use after free in CMS Signing


Affected versions of the OpenSSL crate used structures after they'd been freed.

chrono: Potential segfault in `localtime_r` invocations



Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.


No workarounds are known.


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


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.