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-test(17 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-codec | ^0.5 | 0.5.2 | up to date |
| actix-http | ^3.7 | 3.9.0 | up to date |
| actix-http-test | ^3 | 3.2.0 | up to date |
| actix-rt | ^2.1 | 2.10.0 | up to date |
| actix-service | ^2 | 2.0.2 | up to date |
| actix-utils | ^3 | 3.0.1 | up to date |
| actix-web | ^4.6 | 4.9.0 | up to date |
| awc | ^3.5 | 3.5.1 | up to date |
| futures-core | ^0.3.17 | 0.3.31 | up to date |
| futures-util | ^0.3.17 | 0.3.31 | up to date |
| log | ^0.4 | 0.4.25 | up to date |
| serde | ^1 | 1.0.217 | up to date |
| serde_json | ^1 | 1.0.137 | up to date |
| serde_urlencoded | ^0.7 | 0.7.1 | up to date |
| openssl ⚠️ | ^0.10.55 | 0.10.68 | maybe insecure |
| rustls ⚠️ | ^0.23 | 0.23.21 | maybe insecure |
| tokio | ^1.24.2 | 1.43.0 | up to date |
openssl: `MemBio::get_buf` has undefined behavior with empty buffersPreviously, MemBio::get_buf called slice::from_raw_parts with a null-pointer, which violates the functions invariants, leading to undefined behavior. In debug builds this would produce an assertion failure. This is now fixed.
rustls: rustls network-reachable panic in `Acceptor::accept`A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept() are affected.
Servers that use tokio-rustls's LazyConfigAcceptor API are affected.
Servers that use tokio-rustls's TlsAcceptor API are not affected.
Servers that use rustls-ffi's rustls_acceptor_accept API are affected.