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.

Crate ntex-connect

Dependencies

(15 total, 10 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 log^0.40.4.22up to date
 ntex-async-std^0.1.10.5.1out of date
 ntex-bytes^0.1.150.1.27up to date
 ntex-glommio^0.1.20.5.2out of date
 ntex-http^0.1.80.1.12up to date
 ntex-io^0.1.112.8.3out of date
 ntex-rt^0.4.50.4.20up to date
 ntex-service^0.3.13.3.3out of date
 ntex-tls^0.1.52.3.0out of date
 ntex-tokio^0.1.30.5.3out of date
 ntex-util^0.1.182.5.0out of date
 thiserror^1.02.0.3out of date
 openssl ⚠️^0.100.10.68maybe insecure
 rustls ⚠️^0.200.23.16out of date
 webpki-roots^0.220.26.6out of date

Dev dependencies

(3 total, 2 outdated)

CrateRequiredLatestStatus
 env_logger^0.100.11.5out of date
 ntex^0.52.8.0out of date
 rand^0.80.8.5up to date

Security Vulnerabilities

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If 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 buffers

RUSTSEC-2024-0357

Previously, 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.