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-server

Dependencies

(23 total, 2 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.430.1.57up to date
 bytes^11.2.1up to date
 cfg-if^11.0.0up to date
 enum-as-inner^0.50.5.1up to date
 futures-executor^0.3.50.3.24up to date
 futures-util^0.3.50.3.24up to date
 h2^0.3.00.3.14up to date
 http^0.20.2.8up to date
 openssl ⚠️^0.100.10.42maybe insecure
 rusqlite^0.28.00.28.0up to date
 rustls^0.200.20.6up to date
 serde^1.0.1141.0.145up to date
 thiserror^1.0.201.0.37up to date
 time^0.30.3.14up to date
 tokio ⚠️^1.01.21.2maybe insecure
 tokio-openssl^0.6.00.6.3up to date
 tokio-rustls^0.23.00.23.4up to date
 toml^0.50.5.9up to date
 tracing^0.1.300.1.36up to date
 trust-dns-client^0.22.00.22.0up to date
 trust-dns-proto^0.22.00.22.0up to date
 trust-dns-recursor^0.22.00.22.0up to date
 trust-dns-resolver^0.22.00.22.0up to date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.01.21.2maybe insecure
 tracing-subscriber^0.30.3.15up to date

Security Vulnerabilities

openssl: Use after free in CMS Signing

RUSTSEC-2018-0010

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

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.