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.
awc(17 total, 9 outdated, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-codec ⚠️ | ^0.2.0 | 0.5.2 | out of date |
| actix-http ⚠️ | ^2.0.0-alpha.2 | 3.6.0 | out of date |
| actix-rt | ^1.0.0 | 2.9.0 | out of date |
| actix-service | ^1.0.1 | 2.0.2 | out of date |
| base64 | ^0.11 | 0.22.0 | out of date |
| bytes | ^0.5.3 | 1.6.0 | out of date |
| derive_more | ^0.99.2 | 0.99.17 | up to date |
| futures-core | ^0.3.1 | 0.3.30 | up to date |
| log | ^0.4 | 0.4.21 | up to date |
| mime | ^0.3 | 0.3.17 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.64 | maybe insecure |
| percent-encoding | ^2.1 | 2.3.1 | up to date |
| rand | ^0.7 | 0.8.5 | out of date |
| rustls ⚠️ | ^0.17.0 | 0.23.5 | out of date |
| serde | ^1.0 | 1.0.198 | up to date |
| serde_json | ^1.0 | 1.0.116 | up to date |
| serde_urlencoded | ^0.6.1 | 0.7.1 | out of date |
(12 total, 8 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-connect | ^2.0.0-alpha.2 | 2.0.0 | up to date |
| actix-http ⚠️ | ^2.0.0-alpha.2 | 3.6.0 | out of date |
| actix-http-test | ^1.0.0 | 3.2.0 | out of date |
| actix-server | ^1.0.0 | 2.3.0 | out of date |
| actix-tls | ^2.0.0-alpha.1 | 3.3.0 | out of date |
| actix-utils | ^1.0.3 | 3.0.1 | out of date |
| actix-web | ^2.0.0 | 4.5.1 | out of date |
| brotli2 | ^0.3.2 | 0.3.2 | up to date |
| env_logger | ^0.7 | 0.11.3 | out of date |
| flate2 | ^1.0.13 | 1.0.28 | up to date |
| futures | ^0.3.1 | 0.3.30 | up to date |
| webpki ⚠️ | ^0.21 | 0.22.4 | out of date |
actix-codec: Use-after-free in Framed due to lack of pinningAffected versions of this crate did not require the buffer wrapped in Framed to be pinned,
but treated it as if it had a fixed location in memory. This may result in a use-after-free.
The flaw was corrected by making the affected functions accept Pin<&mut Self> instead of &mut self.
actix-http: Potential request smuggling capabilities due to lack of input validationAffected 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.
openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-readWhen this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.
webpki: webpki: CPU denial of service in certificate path buildingWhen this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.
Both TLS clients and TLS servers that accept client certificate are affected.
This was previously reported in https://github.com/briansmith/webpki/issues/69 and re-reported recently by Luke Malinowski.
webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf 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.