This project contains known security vulnerabilities. Find detailed information at the bottom.
awc(16 total, 9 outdated, 2 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-codec ⚠️ | ^0.2.0-alpha.2 | 0.5.4 | insecure |
| actix-http ⚠️ | ^0.3.0-alpha.2 | 3.13.7 | insecure |
| actix-rt | ^1.0.0-alpha.2 | 2.15.0 | out of date |
| actix-service | ^1.0.0-alpha.2 | 2.0.3 | out of date |
| base64 | ^0.10.1 | 0.23.1 | out of date |
| bytes | ^0.4 | 1.12.1 | out of date |
| derive_more | ^0.99.2 | 2.1.1 | out of date |
| futures | ^0.3.1 | 0.3.34 | up to date |
| log | ^0.4 | 0.4.34 | up to date |
| mime | ^0.3 | 0.3.17 | up to date |
| openssl | ^0.10 | 0.10.81 | up to date |
| percent-encoding | ^2.1 | 2.3.2 | up to date |
| rand | ^0.7 | 0.10.3 | out of date |
| serde | ^1.0 | 1.0.229 | up to date |
| serde_json | ^1.0 | 1.0.151 | up to date |
| serde_urlencoded | ^0.6.1 | 0.7.1 | out of date |
(11 total, 9 outdated, 2 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-connect | ^1.0.0-alpha.2 | 2.0.0 | out of date |
| actix-http ⚠️ | ^0.3.0-alpha.2 | 3.13.7 | insecure |
| actix-http-test | ^0.3.0-alpha.2 | 3.3.0 | out of date |
| actix-server | ^1.0.0-alpha.2 | 2.9.5 | out of date |
| actix-utils | ^1.0.0-alpha.2 | 3.0.2 | out of date |
| actix-web | ^2.0.0-alpha.1 | 4.15.0 | out of date |
| brotli2 | ^0.3.2 | 0.3.2 | up to date |
| env_logger | ^0.6 | 0.11.11 | out of date |
| flate2 | ^1.0.2 | 1.1.10 | up to date |
| rand | ^0.7 | 0.10.3 | out of date |
| webpki ⚠️ | ^0.21 | 0.22.4 | insecure |
actix-http: Use-after-free in BodyStream due to lack of pinningAffected versions of this crate did not require the buffer wrapped in BodyStream 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 trait MessageBody require Unpin
and making poll_next() function accept Pin<&mut Self> instead of &mut self.
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.
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.