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 actix

Dependencies

(19 total, 12 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 actix-http ⚠️^0.2.03.9.0out of date
 actix-rt^0.2.22.10.0out of date
 actix_derive^0.40.6.2out of date
 bitflags^1.02.6.0out of date
 bytes^0.41.8.0out of date
 crossbeam-channel^0.30.5.13out of date
 derive_more^0.14.01.0.0out of date
 futures^0.1.250.3.31out of date
 hashbrown^0.3.00.15.1out of date
 lazy_static^1.21.5.0up to date
 log^0.40.4.22up to date
 parking_lot^0.80.12.3out of date
 smallvec ⚠️^0.61.13.2out of date
 tokio-codec^0.10.1.2up to date
 tokio-executor^0.10.1.10up to date
 tokio-io^0.10.1.13up to date
 tokio-tcp^0.10.1.4up to date
 tokio-timer^0.2.80.2.13up to date
 trust-dns-resolver^0.11.00.23.2out of date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 doc-comment^0.30.3.3up to date

Security Vulnerabilities

actix-http: Use-after-free in BodyStream due to lack of pinning

RUSTSEC-2020-0048

Affected 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.

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.

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.