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(37 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22 | 0.22.1 | up to date |
| bitflags | ^2 | 2.9.1 | up to date |
| cookie | ^0.18 | 0.18.1 | up to date |
| encoding_rs | ^0.8 | 0.8.35 | up to date |
| env_logger | ^0.11 | 0.11.8 | up to date |
| flate2 | ^1.0 | 1.1.2 | up to date |
| httparse | ^1.9 | 1.10.1 | up to date |
| httpdate | ^1.0 | 1.0.3 | up to date |
| log | ^0.4 | 0.4.27 | up to date |
| mime | ^0.3 | 0.3.17 | up to date |
| nanorand | ^0.8 | 0.8.0 | up to date |
| ntex-bytes | ^0.1.28 | 0.1.28 | up to date |
| ntex-codec | ^0.6 | 0.6.2 | up to date |
| ntex-h2 | ^1.9.0 | 1.9.0 | up to date |
| ntex-http | ^0.1.13 | 0.1.13 | up to date |
| ntex-io | ^2.13.2 | 2.13.2 | up to date |
| ntex-macros | ^0.1 | 0.1.4 | up to date |
| ntex-net | ^2.5.27 | 2.5.27 | up to date |
| ntex-router | ^0.5 | 0.5.3 | up to date |
| ntex-rt | ^0.4.31 | 0.4.31 | up to date |
| ntex-server | ^2.8.1 | 2.8.1 | up to date |
| ntex-service | ^3.4 | 3.5.0 | up to date |
| ntex-tls | ^2.3 | 2.4.1 | up to date |
| ntex-util | ^2.12 | 2.12.0 | up to date |
| percent-encoding | ^2.3 | 2.3.1 | up to date |
| pin-project-lite | ^0.2 | 0.2.16 | up to date |
| regex | ^1.11 | 1.11.1 | up to date |
| serde | ^1 | 1.0.219 | up to date |
| serde_json | ^1 | 1.0.140 | up to date |
| serde_urlencoded | ^0.7 | 0.7.1 | up to date |
| sha-1 | ^0.10 | 0.10.1 | up to date |
| thiserror | ^2 | 2.0.12 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.73 | maybe insecure |
| rustls ⚠️ | ^0.23 | 0.23.28 | maybe insecure |
| url | ^2.5 | 2.5.4 | up to date |
| variadics_please | ^1.1 | 1.1.0 | up to date |
| webpki-roots | ^1.0 | 1.0.1 | up to date |
(8 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-util | ^0.3.29 | 0.3.31 | up to date |
| oneshot | ^0.1 | 0.1.11 | up to date |
| rand | ^0.9 | 0.9.1 | up to date |
| rustls-pemfile | ^2 | 2.2.0 | up to date |
| time | ^0.3 | 0.3.41 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.73 | maybe insecure |
| rustls ⚠️ | ^0.23 | 0.23.28 | maybe insecure |
| webpki-roots | ^1.0 | 1.0.1 | up to 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.