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

Crate trust-dns-server

Dependencies

(26 total, 1 outdated, 2 insecure)

CrateRequiredLatestStatus
 async-trait^0.1.420.1.50up to date
 bytes^11.0.1up to date
 cfg-if^11.0.0up to date
 chrono^0.40.4.19up to date
 enum-as-inner^0.30.3.3up to date
 env_logger^0.80.8.3up to date
 futures-executor^0.3.50.3.14up to date
 futures-util^0.3.50.3.14insecure
 h2^0.3.00.3.2up to date
 http^0.20.2.4up to date
 log^0.40.4.14up to date
 openssl^0.100.10.33insecure
 rusqlite^0.24.00.25.1out of date
 rustls^0.190.19.1up to date
 serde^1.0.1141.0.125up to date
 thiserror^1.0.201.0.24up to date
 tokio^1.01.5.0up to date
 tokio-openssl^0.6.00.6.1up to date
 tokio-rustls^0.220.22.0up to date
 toml^0.50.5.8up to date
 trust-dns-client^0.20.10.20.2up to date
 trust-dns-https^0.20.10.20.2up to date
 trust-dns-openssl^0.20.10.20.2up to date
 trust-dns-proto^0.20.10.20.2up to date
 trust-dns-resolver^0.20.10.20.2up to date
 trust-dns-rustls^0.20.10.20.2up 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.

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.