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, 7 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 actix-codec^0.50.5.2up to date
 actix-http^3.33.6.0up to date
 actix-rt^2.12.9.0up to date
 actix-service^22.0.2up to date
 actix-tls^33.3.0up to date
 actix-utils^33.0.1up to date
 ahash^0.70.8.11out of date
 base64^0.210.22.0out of date
 bytes^11.6.0up to date
 cfg-if^11.0.0up to date
 cookie^0.160.18.1out of date
 derive_more^0.99.50.99.17up to date
 futures-core^0.3.170.3.30up to date
 futures-util^0.3.170.3.30up to date
 h2 ⚠️^0.3.90.4.4out of date
 http^0.2.51.1.0out of date
 itoa^11.0.11up to date
 log^0.40.4.21up to date
 mime^0.30.3.17up to date
 percent-encoding^2.12.3.1up to date
 pin-project-lite^0.20.2.14up to date
 rand^0.80.8.5up to date
 serde^1.01.0.198up to date
 serde_json^1.01.0.116up to date
 serde_urlencoded^0.70.7.1up to date
 openssl ⚠️^0.10.90.10.64maybe insecure
 rustls^0.20.00.23.4out of date
 tokio ⚠️^1.18.41.37.0maybe insecure
 trust-dns-resolver^0.220.23.2out of 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);

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.

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.