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

Dependencies

(18 total, 5 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 cfg-if^11.0.0up to date
 chrono ⚠️^0.40.4.38maybe insecure
 data-encoding^2.2.02.5.0up to date
 futures-channel^0.3.50.3.30up to date
 futures-util^0.3.50.3.30up to date
 lazy_static^1.01.4.0up to date
 log^0.40.4.21up to date
 openssl ⚠️^0.100.10.64maybe insecure
 radix_trie^0.2.00.2.1up to date
 rand^0.80.8.5up to date
 ring^0.160.17.8out of date
 rustls^0.190.23.4out of date
 serde^1.01.0.198up to date
 thiserror^1.0.201.0.58up to date
 tokio ⚠️^1.01.37.0maybe insecure
 trust-dns-https^0.20.00.21.1out of date
 trust-dns-proto^0.20.00.23.2out of date
 webpki ⚠️^0.210.22.4out of date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.3.50.3.30up to date
 openssl ⚠️^0.100.10.64maybe insecure

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.

webpki: webpki: CPU denial of service in certificate path building

RUSTSEC-2023-0052

When this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.

Both TLS clients and TLS servers that accept client certificate are affected.

This was previously reported in https://github.com/briansmith/webpki/issues/69 and re-reported recently by Luke Malinowski.

webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.