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

Dependencies

(19 total, 10 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.40.4.37maybe insecure
 data-encoding^2.1.02.5.0up to date
 data-encoding-macro^0.1.10.1.14up to date
 failure^0.10.1.8up to date
 futures^0.1.260.3.30out of date
 lazy_static^1.01.4.0up to date
 log^0.4.10.4.21up to date
 openssl ⚠️^0.100.10.64maybe insecure
 radix_trie^0.1.20.2.1out of date
 rand^0.60.8.5out of date
 ring^0.140.17.8out of date
 rustls^0.150.23.4out of date
 serde^1.01.0.197up to date
 tokio ⚠️^0.1.151.36.0out of date
 tokio-tcp^0.10.1.4up to date
 trust-dns-https^0.3.00.21.1out of date
 trust-dns-proto^0.7.30.23.2out of date
 untrusted^0.60.9.0out of date
 webpki ⚠️^0.190.22.4out of date

Dev dependencies

(1 total, 1 possibly insecure)

CrateRequiredLatestStatus
 openssl ⚠️^0.100.10.64maybe insecure

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

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.

Workarounds

No workarounds are known.

References

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.

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

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

RUSTSEC-2023-0052

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

webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.