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 awc

Dependencies

(29 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-codec^0.50.5.0up to date
 actix-http^3.33.3.1up to date
 actix-rt^2.12.8.0up to date
 actix-service^22.0.2up to date
 actix-tls^33.0.3up to date
 actix-utils^33.0.1up to date
 ahash^0.70.8.3out of date
 base64^0.210.21.0up to date
 bytes^11.4.0up to date
 cfg-if^11.0.0up to date
 cookie^0.160.17.0out of date
 derive_more^0.99.50.99.17up to date
 futures-core^0.3.170.3.27up to date
 futures-util^0.3.170.3.27up to date
 h2^0.3.90.3.16up to date
 http^0.2.50.2.9up to date
 itoa^11.0.6up to date
 log^0.40.4.17up to date
 mime^0.30.3.17up to date
 percent-encoding^2.12.2.0up to date
 pin-project-lite^0.20.2.9up to date
 rand^0.80.8.5up to date
 serde^1.01.0.158up to date
 serde_json^1.01.0.94up to date
 serde_urlencoded^0.70.7.1up to date
 openssl^0.10.90.10.48up to date
 rustls^0.20.00.20.8up to date
 tokio ⚠️^1.18.41.26.0maybe insecure
 trust-dns-resolver^0.220.22.0up 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);