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

(23 total, 6 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.430.1.80up to date
 bytes^11.6.0up to date
 cfg-if^11.0.0up to date
 drain^0.1.10.1.2up to date
 enum-as-inner^0.60.6.0up to date
 futures-executor^0.3.50.3.30up to date
 futures-util^0.3.50.3.30up to date
 h2 ⚠️^0.3.00.4.5out of date
 http^0.21.1.0out of date
 openssl^0.10.550.10.64up to date
 rusqlite^0.29.00.31.0out of date
 rustls ⚠️^0.21.00.23.9out of date
 serde^1.01.0.203up to date
 thiserror^1.0.201.0.61up to date
 time^0.30.3.36up to date
 tokio ⚠️^1.211.38.0maybe insecure
 tokio-openssl^0.6.00.6.4up to date
 tokio-rustls^0.24.00.26.0out of date
 toml^0.70.8.14out of date
 tracing^0.1.300.1.40up to date
 trust-dns-proto^0.23.20.23.2up to date
 trust-dns-recursor^0.23.20.23.2up to date
 trust-dns-resolver^0.23.20.23.2up to date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.211.38.0maybe insecure
 tracing-subscriber^0.30.3.18up to date

Security Vulnerabilities

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.