Affected versions of the OpenSSL crate used structures after they'd been freed.
This project contains known security vulnerabilities. Find detailed information at the bottom.
trust-dns-server
(26 total, 2 insecure)
Crate | Required | Latest | Status |
---|---|---|---|
async-trait | ^0.1.42 | 0.1.42 | up to date |
bytes | ^1 | 1.0.1 | up to date |
cfg-if | ^1 | 1.0.0 | up to date |
chrono | ^0.4 | 0.4.19 | up to date |
enum-as-inner | ^0.3 | 0.3.3 | up to date |
env_logger | ^0.8 | 0.8.3 | up to date |
futures-executor | ^0.3.5 | 0.3.13 | up to date |
futures-util | ^0.3.5 | 0.3.13 | insecure |
h2 | ^0.3.0 | 0.3.1 | up to date |
http | ^0.2 | 0.2.3 | up to date |
log | ^0.4 | 0.4.14 | up to date |
openssl | ^0.10 | 0.10.32 | insecure |
rusqlite | ^0.24.0 | 0.24.2 | up to date |
rustls | ^0.19 | 0.19.0 | up to date |
serde | ^1.0.114 | 1.0.123 | up to date |
thiserror | ^1.0.20 | 1.0.24 | up to date |
tokio | ^1.0 | 1.2.0 | up to date |
tokio-openssl | ^0.6.0 | 0.6.1 | up to date |
tokio-rustls | ^0.22 | 0.22.0 | up to date |
toml | ^0.5 | 0.5.8 | up to date |
trust-dns-client | ^0.20.0 | 0.20.0 | up to date |
trust-dns-https | ^0.20.0 | 0.20.0 | up to date |
trust-dns-openssl | ^0.20.0 | 0.20.0 | up to date |
trust-dns-proto | ^0.20.0 | 0.20.0 | up to date |
trust-dns-resolver | ^0.20.0 | 0.20.0 | up to date |
trust-dns-rustls | ^0.20.0 | 0.20.0 | up to date |
openssl
: Use after free in CMS SigningAffected versions of the OpenSSL crate used structures after they'd been freed.
futures-util
: MutexGuard::map can cause a data race in safe codeAffected 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.