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

(18 total, 9 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 actix-codec^0.3.00.5.2out of date
 actix-http ⚠️^2.2.03.9.0out of date
 actix-rt^1.0.02.10.0out of date
 actix-service^1.0.62.0.2out of date
 base64^0.130.22.1out of date
 bytes^0.5.31.8.0out of date
 cfg-if^1.01.0.0up to date
 derive_more^0.99.21.0.0out of date
 futures-core^0.3.50.3.31up to date
 log^0.40.4.22up to date
 mime^0.30.3.17up to date
 openssl ⚠️^0.100.10.68maybe insecure
 percent-encoding^2.12.3.1up to date
 rand^0.70.8.5out of date
 rustls ⚠️^0.18.00.23.16out of date
 serde^1.01.0.214up to date
 serde_json^1.01.0.132up to date
 serde_urlencoded^0.70.7.1up to date

Security Vulnerabilities

actix-http: Potential request smuggling capabilities due to lack of input validation

RUSTSEC-2021-0081

Affected versions of this crate did not properly detect invalid requests that could allow HTTP/1 request smuggling (HRS) attacks when running alongside a vulnerable front-end proxy server. This can result in leaked internal and/or user data, including credentials, when the front-end proxy is also vulnerable.

Popular front-end proxies and load balancers already mitigate HRS attacks so it is recommended that they are also kept up to date; check your specific set up. You should upgrade even if the front-end proxy receives exclusively HTTP/2 traffic and connects to the back-end using HTTP/1; several downgrade attacks are known that can also expose HRS vulnerabilities.

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.

openssl: `MemBio::get_buf` has undefined behavior with empty buffers

RUSTSEC-2024-0357

Previously, MemBio::get_buf called slice::from_raw_parts with a null-pointer, which violates the functions invariants, leading to undefined behavior. In debug builds this would produce an assertion failure. This is now fixed.