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-connect(13 total, 8 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-codec ⚠️ | ^0.1.2 | 0.5.2 | out of date |
| actix-service | ^0.3.6 | 2.0.3 | out of date |
| actix-utils | ^0.3.5 | 3.0.1 | out of date |
| derive_more | ^0.14.0 | 2.0.1 | out of date |
| either | ^1.5.2 | 1.15.0 | up to date |
| futures | ^0.1.25 | 0.3.31 | out of date |
| http ⚠️ | ^0.1.17 | 1.3.1 | out of date |
| log | ^0.4 | 0.4.27 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.73 | maybe insecure |
| tokio-current-thread | ^0.1.5 | 0.1.7 | up to date |
| tokio-openssl | ^0.3 | 0.6.5 | out of date |
| tokio-tcp | ^0.1.3 | 0.1.4 | up to date |
| trust-dns-resolver | ^0.11.0 | 0.23.2 | out of date |
(5 total, 3 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-server-config | ^0.1.0 | 0.2.0 | out of date |
| actix-test-server | ^0.2.1 | 0.2.2 | up to date |
| actix-utils | ^0.3.4 | 3.0.1 | out of date |
| bytes | ^0.4 | 1.10.1 | out of date |
| tokio-tcp | ^0.1 | 0.1.4 | up to date |
http: Integer Overflow in HeaderMap::reserve() can cause Denial of ServiceHeaderMap::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 unsoundAffected versions of this crate incorrectly used raw pointer, which introduced unsoundness in its public safe API.
Failing to drop the Drain struct causes double-free, and it is possible to violate Rust's alias rule and cause data race with Drain's Iterator implementation.
The flaw was corrected in 0.1.20 release of http crate.
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.
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.