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 wreq

Dependencies

(42 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 antidote^11.0.0up to date
 arc-swap^1.7.01.7.1up to date
 async-compression^0.4.210.4.32up to date
 base64^0.220.22.1up to date
 boring2^4.15.114.15.15up to date
 bytes^1.10.11.10.1up to date
 cookie^0.180.18.1up to date
 cookie_store^0.210.22.0out of date
 encoding_rs^0.80.8.35up to date
 futures-util^0.3.00.3.31up to date
 hickory-resolver^0.25.10.25.2up to date
 http^11.3.1up to date
 http-body^11.0.1up to date
 http-body-util^0.10.1.3up to date
 hyper2^1.5.51.5.5up to date
 ipnet^2.11.02.11.0up to date
 libc^0.20.2.177up to date
 linked_hash_set^0.10.1.5up to date
 log^0.4.270.4.28up to date
 lru^0.130.16.1out of date
 mime^0.3.170.3.17up to date
 mime_guess^2.02.0.5up to date
 percent-encoding^2.32.3.2up to date
 pin-project-lite^0.2.00.2.16up to date
 rustls-native-certs^0.8.00.8.1up to date
 serde^1.01.0.228up to date
 serde_json^1.01.0.145up to date
 serde_urlencoded^0.7.10.7.1up to date
 socket2^0.5.80.6.0out of date
 sync_wrapper^1.01.0.2up to date
 system-configuration^0.6.00.6.1up to date
 tokio ⚠️^11.47.1maybe insecure
 tokio-boring2^4.15.114.15.15up to date
 tokio-socks^0.5.20.5.2up to date
 tokio-tungstenite^0.26.20.28.0out of date
 tokio-util^0.7.00.7.16up to date
 tower^0.5.20.5.2up to date
 tower-service^0.30.3.3up to date
 typed-builder^0.21.00.22.0out of date
 url^2.52.5.7up to date
 webpki-root-certs^0.26.01.0.3out of date
 windows-registry^0.5.00.6.1out of date

Dev dependencies

(14 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 brotli^7.0.08.0.2out of date
 doc-comment^0.30.3.3up to date
 env_logger^0.11.60.11.8up to date
 futures^0.3.00.3.31up to date
 hyper^1.1.01.7.0up to date
 hyper-util^0.1.100.1.17up to date
 libc^0.20.2.177up to date
 libflate^2.0.02.1.0up to date
 serde^1.01.0.228up to date
 tokio ⚠️^1.01.47.1maybe insecure
 tower^0.5.20.5.2up to date
 tracing^0.10.1.41up to date
 tracing-subscriber^0.3.190.3.20up to date
 zstd^0.130.13.3up 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);