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.
actix-framed(9 total, 8 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-codec ⚠️ | ^0.1.2 | 0.5.2 | out of date |
| actix-http ⚠️ | ^0.2.7 | 3.6.0 | out of date |
| actix-router | ^0.1.2 | 0.5.2 | out of date |
| actix-rt | ^0.2.2 | 2.9.0 | out of date |
| actix-server-config | ^0.1.2 | 0.2.0 | out of date |
| actix-service | ^0.4.1 | 2.0.2 | out of date |
| bytes | ^0.4 | 1.6.0 | out of date |
| futures | ^0.1.25 | 0.3.30 | out of date |
| log | ^0.4 | 0.4.21 | up to date |
(4 total, 4 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-connect | ^0.2.0 | 2.0.0 | out of date |
| actix-http-test | ^0.2.4 | 3.2.0 | out of date |
| actix-server | ^0.6.0 | 2.3.0 | out of date |
| actix-utils | ^0.4.4 | 3.0.1 | out of 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-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.