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

Crate trust-dns-client

Dependencies

(18 total, 1 outdated, 2 insecure)

CrateRequiredLatestStatus
 cfg-if^11.0.0up to date
 chrono^0.40.4.19up to date
 data-encoding^2.2.02.3.2up to date
 futures-channel^0.3.50.3.14up to date
 futures-util^0.3.50.3.14insecure
 lazy_static^1.01.4.0up to date
 log^0.40.4.14up to date
 openssl^0.100.10.33insecure
 radix_trie^0.2.00.2.1up to date
 rand^0.80.8.3up to date
 ring^0.160.16.20up to date
 rustls^0.190.19.1up to date
 serde^1.01.0.125up to date
 thiserror^1.0.201.0.24up to date
 tokio^1.01.5.0up to date
 trust-dns-https^0.20.10.20.2up to date
 trust-dns-proto^0.20.10.20.2up to date
 webpki^0.210.22.0out of date

Dev dependencies

(2 total, 1 insecure)

CrateRequiredLatestStatus
 futures^0.3.50.3.14up to date
 openssl^0.100.10.33insecure

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.

futures-util: MutexGuard::map can cause a data race in safe code

RUSTSEC-2020-0059

Affected versions of the crate had a Send/Sync implementation for MappedMutexGuard that only considered variance on T, while MappedMutexGuard dereferenced to U.

This could of led to data races in safe Rust code when a closure used in MutexGuard::map() returns U that is unrelated to T.

The issue was fixed by fixing Send and Sync implementations, and by adding a PhantomData<&'a mut U> marker to the MappedMutexGuard type to tell the compiler that the guard is over U too.