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 reqwest

Dependencies

(54 total, 1 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 async-compression^0.4.00.4.18up to date
 base64^0.220.22.1up to date
 bytes^1.01.9.0up to date
 cookie^0.18.00.18.1up to date
 cookie_store^0.21.00.21.1up to date
 encoding_rs^0.80.8.35up to date
 futures-channel^0.30.3.31up to date
 futures-core^0.3.280.3.31up to date
 futures-util^0.3.280.3.31up to date
 h2 ⚠️^0.40.4.7maybe insecure
 h3^0.0.60.0.6up to date
 h3-quinn^0.0.70.0.7up to date
 hickory-resolver^0.240.24.2up to date
 http^11.2.0up to date
 http-body^11.0.1up to date
 http-body-util^0.10.1.2up to date
 hyper^1.11.5.2up to date
 hyper-rustls^0.27.00.27.5up to date
 hyper-tls^0.60.6.0up to date
 hyper-util^0.1.100.1.10up to date
 ipnet^2.32.10.1up to date
 js-sys^0.3.450.3.76up to date
 log^0.4.170.4.22up to date
 mime^0.3.160.3.17up to date
 mime_guess^2.02.0.5up to date
 native-tls^0.2.100.2.12up to date
 once_cell^1.181.20.2up to date
 percent-encoding^2.32.3.1up to date
 pin-project-lite^0.2.110.2.15up to date
 quinn^0.11.10.11.6up to date
 rustls ⚠️^0.23.40.23.20maybe insecure
 rustls-native-certs^0.8.00.8.1up to date
 rustls-pemfile^22.2.0up to date
 rustls-pki-types^1.1.01.10.1up to date
 serde^1.01.0.217up to date
 serde_json^1.01.0.134up to date
 serde_urlencoded^0.7.10.7.1up to date
 slab^0.4.90.4.9up to date
 sync_wrapper^1.01.0.2up to date
 system-configuration^0.6.00.6.1up to date
 tokio ⚠️^1.01.42.0maybe insecure
 tokio-native-tls^0.3.00.3.1up to date
 tokio-rustls^0.260.26.1up to date
 tokio-socks^0.5.20.5.2up to date
 tokio-util^0.7.90.7.13up to date
 tower^0.5.20.5.2up to date
 tower-service^0.30.3.3up to date
 url^2.42.5.4up to date
 wasm-bindgen^0.2.890.2.99up to date
 wasm-bindgen-futures^0.4.180.4.49up to date
 wasm-streams^0.40.4.2up to date
 web-sys^0.3.280.3.76up to date
 webpki-roots^0.26.00.26.7up to date
 windows-registry^0.20.3.0out of date

Dev dependencies

(16 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 brotli^6.0.07.0.0out of date
 doc-comment^0.30.3.3up to date
 env_logger^0.100.11.6out of date
 futures-util^0.3.280.3.31up to date
 hyper^1.1.01.5.2up to date
 hyper-util^0.1.100.1.10up to date
 libc^00.2.169up to date
 libflate^2.12.1.0up to date
 num_cpus^1.01.16.0up to date
 rustls ⚠️^0.230.23.20maybe insecure
 serde^1.01.0.217up to date
 tokio ⚠️^1.01.42.0maybe insecure
 tower^0.5.20.5.2up to date
 wasm-bindgen^0.2.890.2.99up to date
 wasm-bindgen-test^0.30.3.49up to date
 zstd^0.130.13.2up 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 network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.