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.
ntex-tls(8 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| log | ^0.4 | 0.4.27 | up to date |
| ntex-bytes | ^0.1 | 0.1.28 | up to date |
| ntex-io | ^2.3 | 2.13.2 | up to date |
| ntex-net | ^2 | 2.5.27 | up to date |
| ntex-service | ^3.4 | 3.5.0 | up to date |
| ntex-util | ^2.5 | 2.12.0 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.73 | maybe insecure |
| rustls ⚠️ | ^0.23 | 0.23.28 | maybe insecure |
(5 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.11 | 0.11.8 | up to date |
| ntex | ^2 | 2.13.2 | up to date |
| rustls-pemfile | ^2 | 2.2.0 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.28 | maybe insecure |
| webpki-roots | ^0.26 | 1.0.1 | out of date |
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.
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.