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

Dependencies

(24 total, 1 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.360.1.52up to date
 backtrace^0.3.500.3.63up to date
 cfg-if^11.0.0up to date
 data-encoding^2.2.02.3.2up to date
 enum-as-inner^0.30.3.3up to date
 futures-channel^0.3.50.3.19up to date
 futures-io^0.3.50.3.19up to date
 futures-util^0.3.50.3.19up to date
 idna^0.2.00.2.3up to date
 ipnet^2.3.02.3.1up to date
 js-sys^0.3.440.3.55up to date
 lazy_static^1.01.4.0up to date
 log^0.40.4.14up to date
 openssl ⚠️^0.100.10.38maybe insecure
 rand^0.80.8.4up to date
 ring^0.160.16.20up to date
 serde^1.01.0.133up to date
 smallvec ⚠️^1.61.8.0maybe insecure
 socket2^0.3.160.4.2out of date
 thiserror^1.0.201.0.30up to date
 tinyvec^1.1.11.5.1up to date
 tokio ⚠️^1.01.15.0maybe insecure
 url^2.1.02.2.2up to date
 wasm-bindgen^0.2.580.2.78up to date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.80.9.0out of date
 futures-executor^0.3.50.3.19up to date
 tokio ⚠️^1.01.15.0maybe insecure

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.

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: 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.