This project contains known security vulnerabilities. Find detailed information at the bottom.
ntex(44 total, 21 outdated, 5 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ahash | ^0.7.4 | 0.8.12 | out of date |
| base64 | ^0.13 | 0.23.1 | out of date |
| bitflags | ^1.2 | 2.13.2 | out of date |
| brotli2 | ^0.3.2 | 0.3.2 | up to date |
| bytes | ^1.0 | 1.12.1 | up to date |
| bytestring | ^1.0 | 1.5.1 | up to date |
| cookie | ^0.15 | 0.18.2 | out of date |
| derive_more | ^0.99.13 | 2.1.1 | out of date |
| encoding_rs | ^0.8 | 0.8.41 | up to date |
| flate2 | ^1.0.20 | 1.1.10 | up to date |
| futures-core | ^0.3.15 | 0.3.34 | up to date |
| futures-sink | ^0.3.15 | 0.3.34 | up to date |
| h2 ⚠️ | ^0.3 | 0.4.19 | insecure |
| http | ^0.2 | 1.5.0 | out of date |
| httparse | ^1.3 | 1.10.1 | up to date |
| httpdate | ^1.0 | 1.0.3 | up to date |
| log | ^0.4 | 0.4.34 | up to date |
| mime | ^0.3 | 0.3.17 | up to date |
| mio ⚠️ | ^0.7.10 | 1.2.3 | insecure |
| nanorand ⚠️ | ^0.5 | 0.8.0 | insecure |
| ntex-codec | ^0.4.1 | 1.2.1 | out of date |
| ntex-macros | ^0.1.3 | 4.0.0 | out of date |
| ntex-router | ^0.4.3 | 1.1.0 | out of date |
| ntex-rt | ^0.2.2 | 3.17.3 | out of date |
| ntex-service | ^0.1.9 | 5.0.1 | out of date |
| ntex-util | ^0.1.1 | 4.0.1 | out of date |
| num_cpus | ^1.13 | 1.17.0 | up to date |
| openssl | ^0.10 | 0.10.81 | up to date |
| percent-encoding | ^2.1 | 2.3.2 | up to date |
| pin-project-lite | ^0.2 | 0.2.17 | up to date |
| regex | ^1.4.5 | 1.13.1 | up to date |
| rustls ⚠️ | ^0.19 | 0.23.45 | insecure |
| serde | ^1.0 | 1.0.229 | up to date |
| serde_json | ^1.0 | 1.0.151 | up to date |
| serde_urlencoded | ^0.7 | 0.7.1 | up to date |
| sha-1 | ^0.9 | 0.10.1 | out of date |
| slab | ^0.4 | 0.4.12 | up to date |
| socket2 | ^0.4 | 0.6.5 | out of date |
| tokio | ^1 | 1.53.1 | up to date |
| tokio-openssl | ^0.6.1 | 0.6.5 | up to date |
| tokio-rustls | ^0.22 | 0.26.5 | out of date |
| url | ^2.1 | 2.5.8 | up to date |
| webpki ⚠️ | ^0.21 | 0.22.4 | insecure |
| webpki-roots | ^0.21 | 1.0.9 | out of date |
(7 total, 5 outdated, 2 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.8 | 0.11.11 | out of date |
| futures | ^0.3.15 | 0.3.34 | up to date |
| openssl | ^0.10 | 0.10.81 | up to date |
| rand | ^0.8 | 0.10.2 | out of date |
| rustls ⚠️ | ^0.19 | 0.23.45 | insecure |
| time | ^0.2 | 0.3.55 | out of date |
| webpki ⚠️ | ^0.21 | 0.22.4 | insecure |
nanorand: Aliased mutable references from `tls_rand` & `TlsWyRand`TlsWyRand's implementation of Deref unconditionally dereferences a raw pointer, and returns
multiple mutable references to the same object, which is undefined behavior.
webpki: webpki: CPU denial of service in certificate path buildingWhen this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.
Both TLS clients and TLS servers that accept client certificate are affected.
This was previously reported in https://github.com/briansmith/webpki/issues/69 and re-reported recently by Luke Malinowski.
webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.
mio: Tokens for named pipes may be delivered after deregistrationWhen using named pipes on Windows, mio will under some circumstances return invalid tokens that correspond to named pipes that have already been deregistered from the mio registry. The impact of this vulnerability depends on how mio is used. For some applications, invalid tokens may be ignored or cause a warning or a crash. On the other hand, for applications that store pointers in the tokens, this vulnerability may result in a use-after-free.
For users of Tokio, this vulnerability is serious and can result in a use-after-free in Tokio.
The vulnerability is Windows-specific, and can only happen if you are using named pipes. Other IO resources are not affected.
This vulnerability has been fixed in mio v0.8.11.
All versions of mio between v0.7.2 and v0.8.10 are vulnerable.
Tokio is vulnerable when you are using a vulnerable version of mio AND you are using at least Tokio v1.30.0. Versions of Tokio prior to v1.30.0 will ignore invalid tokens, so they are not vulnerable.
Vulnerable libraries that use mio can work around this issue by detecting and ignoring invalid tokens.
When an IO resource registered with mio has a readiness event, mio delivers that readiness event to the user using a user-specified token. Mio guarantees that when an IO resource is deregistered, then it will never return the token for that IO resource again. However, for named pipes on windows, mio may sometimes deliver the token for a named pipe even though the named pipe has been previously deregistered.
This vulnerability was originally reported in the Tokio issue tracker: tokio-rs/tokio#6369
This vulnerability was fixed in: tokio-rs/mio#1760
Thank you to @rofoun and @radekvit for discovering and reporting this issue.
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.
h2: h2 unbounded empty DATA framesThe h2 crate, used internally by hyper, had a flaw that would accept and queue empty DATA frames without limit. If streams were not actively drained, this could lead to unbounded memory usage, or a panic if the length overflows.
Low severity.
Patched in v0.4.16.