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, 4 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| log | ^0.4 | 0.4.22 | up to date |
| ntex-bytes | ^0.1.21 | 0.1.27 | up to date |
| ntex-io | ^1.0 | 2.8.3 | out of date |
| ntex-net | ^1.0 | 2.4.0 | out of date |
| ntex-service | ^2.0 | 3.3.3 | out of date |
| ntex-util | ^1.0 | 2.5.0 | out of date |
| openssl ⚠️ | ^0.10 | 0.10.68 | maybe insecure |
| rustls ⚠️ | ^0.23 | 0.23.16 | maybe insecure |
(4 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.11 | 0.11.5 | up to date |
| ntex | ^1 | 2.8.0 | out of date |
| rustls-pemfile | ^2 | 2.2.0 | up to date |
| webpki-roots | ^0.26 | 0.26.6 | up to date |
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.
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.