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

Dependencies

(26 total, 15 outdated, 5 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.420.1.88up to date
 bytes^11.10.1up to date
 cfg-if^11.0.1up to date
 chrono ⚠️^0.40.4.41maybe insecure
 enum-as-inner^0.30.6.1out of date
 env_logger^0.80.11.8out of date
 futures-executor^0.3.50.3.31up to date
 futures-util^0.3.50.3.31up to date
 h2 ⚠️^0.3.00.4.11out of date
 http^0.21.3.1out of date
 log^0.40.4.27up to date
 openssl ⚠️^0.100.10.73maybe insecure
 rusqlite^0.24.00.36.0out of date
 rustls ⚠️^0.190.23.28out of date
 serde^1.0.1141.0.219up to date
 thiserror^1.0.202.0.12out of date
 tokio ⚠️^1.01.46.0maybe insecure
 tokio-openssl^0.6.00.6.5up to date
 tokio-rustls^0.220.26.2out of date
 toml^0.50.8.23out of date
 trust-dns-client^0.20.10.23.2out of date
 trust-dns-https^0.20.10.21.1out of date
 trust-dns-openssl^0.20.10.21.1out of date
 trust-dns-proto^0.20.10.23.2out of date
 trust-dns-resolver^0.20.10.23.2out of date
 trust-dns-rustls^0.20.10.21.1out of date

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);

h2: Degradation of service in h2 servers with CONTINUATION Flood

RUSTSEC-2024-0332

An attacker can send a flood of CONTINUATION frames, causing h2 to process them indefinitely. This results in an increase in CPU usage.

Tokio task budget helps prevent this from a complete denial-of-service, as the server can still respond to legitimate requests, albeit with increased latency.

More details at "https://seanmonstar.com/blog/hyper-http2-continuation-flood/.

Patches available for 0.4.x and 0.3.x versions.

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.