This project contains known security vulnerabilities. Find detailed information at the bottom.
actix(19 total, 12 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-http ⚠️ | ^0.2.0 | 3.18.12 | insecure |
| actix-rt | ^0.2.2 | 2.15.0 | out of date |
| actix_derive | ^0.4 | 0.6.2 | out of date |
| bitflags | ^1.0 | 2.13.2 | out of date |
| bytes | ^0.4 | 1.12.1 | out of date |
| crossbeam-channel | ^0.3 | 0.5.17 | out of date |
| derive_more | ^0.14.0 | 2.1.1 | out of date |
| futures | ^0.1.25 | 0.3.34 | out of date |
| hashbrown | ^0.3.0 | 0.17.1 | out of date |
| lazy_static | ^1.2 | 1.5.0 | up to date |
| log | ^0.4 | 0.4.34 | up to date |
| parking_lot | ^0.8 | 0.12.5 | out of date |
| smallvec | ^0.6 | 1.16.2 | out of date |
| tokio-codec | ^0.1 | 0.1.2 | up to date |
| tokio-executor | ^0.1 | 0.1.10 | up to date |
| tokio-io | ^0.1 | 0.1.13 | up to date |
| tokio-tcp | ^0.1 | 0.1.4 | up to date |
| tokio-timer | ^0.2.8 | 0.2.13 | up to date |
| trust-dns-resolver | ^0.11.0 | 0.23.2 | out of date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| doc-comment | ^0.3 | 0.3.4 | up to date |
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-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.