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-connect

Dependencies

(13 total, 8 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 actix-codec ⚠️^0.1.20.5.2out of date
 actix-service^0.3.62.0.2out of date
 actix-utils^0.3.53.0.1out of date
 derive_more^0.14.00.99.17out of date
 either^1.5.21.11.0up to date
 futures^0.1.250.3.30out of date
 http ⚠️^0.1.171.1.0out of date
 log^0.40.4.21up to date
 openssl ⚠️^0.100.10.64maybe insecure
 tokio-current-thread^0.1.50.1.7up to date
 tokio-openssl^0.30.6.4out of date
 tokio-tcp^0.1.30.1.4up to date
 trust-dns-resolver^0.11.00.23.2out of date

Dev dependencies

(5 total, 3 outdated)

CrateRequiredLatestStatus
 actix-server-config^0.1.00.2.0out of date
 actix-test-server^0.2.10.2.2up to date
 actix-utils^0.3.43.0.1out of date
 bytes^0.41.6.0out of date
 tokio-tcp^0.10.1.4up to date

Security Vulnerabilities

http: Integer Overflow in HeaderMap::reserve() can cause Denial of Service

RUSTSEC-2019-0033

HeaderMap::reserve() used usize::next_power_of_two() to calculate the increased capacity. However, next_power_of_two() silently overflows to 0 if given a sufficiently large number in release mode.

If the map was not empty when the overflow happens, the library will invoke self.grow(0) and start infinite probing. This allows an attacker who controls the argument to reserve() to cause a potential denial of service (DoS).

The flaw was corrected in 0.1.20 release of http crate.

http: HeaderMap::Drain API is unsound

RUSTSEC-2019-0034

actix-codec: Use-after-free in Framed due to lack of pinning

RUSTSEC-2020-0049

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

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.