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, 13 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22 | 0.22.1 | up to date |
| bitflags | ^2 | 2.11.0 | 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.9 | up to date |
| flate2 | ^1.0 | 1.1.9 | 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.29 | 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.31 | 1.5.0 | out of date |
| ntex-codec | ^0.6 | 1.1.0 | out of date |
| ntex-h2 | ^1.14.2 | 3.6.2 | out of date |
| ntex-http | ^0.1.15 | 1.0.0 | out of date |
| ntex-io | ^2.15.1 | 3.8.0 | out of date |
| ntex-macros | ^0.1 | 3.1.0 | out of date |
| ntex-net | ^2.9.0 | 3.6.3 | out of date |
| ntex-router | ^0.5 | 1.0.0 | out of date |
| ntex-rt | ^0.4.33 | 3.7.1 | out of date |
| ntex-server | ^2.8.1 | 3.7.0 | out of date |
| ntex-service | ^3.5 | 4.4.0 | out of date |
| ntex-tls | ^2.3 | 3.2.1 | out of date |
| ntex-util | ^2.14 | 3.4.0 | out of date |
| percent-encoding | ^2.3 | 2.3.2 | up to date |
| pin-project-lite | ^0.2 | 0.2.16 | up to date |
| regex | ^1.11 | 1.12.3 | up to date |
| serde | ^1 | 1.0.228 | up to date |
| serde_json | ^1 | 1.0.149 | up to date |
| serde_urlencoded | ^0.7 | 0.7.1 | up to date |
| sha1 | ^0.10 | 0.10.6 | up to date |
| thiserror | ^2 | 2.0.18 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.75 | maybe insecure |
| rustls ⚠️ | ^0.23 | 0.23.36 | maybe insecure |
| url | ^2.5.2 | 2.5.8 | up to date |
| variadics_please | ^1.1 | 1.1.0 | up to date |
| webpki-roots | ^1.0 | 1.0.6 | up to date |
(8 total, 1 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-util | ^0.3.29 | 0.3.32 | up to date |
| oneshot | ^0.1 | 0.1.13 | up to date |
| rand | ^0.9 | 0.10.0 | out of date |
| rustls-pemfile | ^2 | 2.2.0 | up to date |
| time ⚠️ | ^0.3 | 0.3.47 | maybe insecure |
| openssl ⚠️ | ^0.10 | 0.10.75 | maybe insecure |
| rustls ⚠️ | ^0.23 | 0.23.36 | maybe insecure |
| webpki-roots | ^1.0 | 1.0.6 | 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.
time: Denial of Service via Stack ExhaustionWhen user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.
A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.
Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.