Deps.rs

ntex 0.5.31

[![dependency status](https://deps.rs/crate/ntex/0.5.31/status.svg)](https://deps.rs/crate/ntex/0.5.31)

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

Dependencies

(43 total, 19 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 async-channel^1.8.02.3.1out of date
 async-oneshot^0.5.00.5.9up to date
 base64^0.130.22.1out of date
 bitflags^1.32.9.1out of date
 brotli2^0.3.20.3.2up to date
 cookie^0.160.18.1out of date
 encoding_rs^0.80.8.35up to date
 flate2^1.0.221.1.2up to date
 httparse^1.6.01.10.1up to date
 httpdate^1.01.0.3up to date
 log^0.40.4.27up to date
 mime^0.30.3.17up to date
 nanorand^0.7.00.8.0out of date
 ntex-async-std^0.1.10.5.1out of date
 ntex-bytes^0.1.160.1.29up to date
 ntex-codec^0.6.20.6.2up to date
 ntex-connect^0.1.01.1.0out of date
 ntex-glommio^0.1.20.5.2out of date
 ntex-h2^0.1.51.11.0out of date
 ntex-http^0.1.80.1.13up to date
 ntex-io^0.1.92.13.3out of date
 ntex-macros^0.1.30.1.4up to date
 ntex-router^0.5.10.5.3up to date
 ntex-rt^0.4.60.4.32up to date
 ntex-service^0.3.23.5.0out of date
 ntex-tls^0.1.52.4.1out of date
 ntex-tokio^0.1.30.5.3out of date
 ntex-util^0.1.182.12.0out of date
 num_cpus^1.131.17.0up to date
 percent-encoding^2.12.3.1up to date
 pin-project-lite^0.20.2.16up to date
 polling^2.5.13.8.0out of date
 regex ⚠️^1.5.41.11.1maybe insecure
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 serde_urlencoded^0.70.7.1up to date
 sha-1^0.100.10.1up to date
 socket2^0.40.5.10out of date
 thiserror^1.02.0.12out of date
 openssl ⚠️^0.100.10.73maybe insecure
 rustls ⚠️^0.200.23.28out of date
 url^2.12.5.4up to date
 webpki-roots^0.221.0.1out of date

Dev dependencies

(8 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.100.11.8out of date
 futures-util^0.30.3.31up to date
 rand^0.80.9.1out of date
 rustls-pemfile^1.0.02.2.0out of date
 time^0.30.3.41up to date
 openssl ⚠️^0.100.10.73maybe insecure
 rustls ⚠️^0.200.23.28out of date
 webpki-roots^0.221.0.1out of date

Security Vulnerabilities

regex: Regexes with large repetitions on empty sub-expressions take a very long time to parse

RUSTSEC-2022-0013

The Rust Security Response WG was notified that the regex crate did not properly limit the complexity of the regular expressions (regex) it parses. An attacker could use this security issue to perform a denial of service, by sending a specially crafted regex to a service accepting untrusted regexes. No known vulnerability is present when parsing untrusted input with trusted regexes.

This issue has been assigned CVE-2022-24713. The severity of this vulnerability is "high" when the regex crate is used to parse untrusted regexes. Other uses of the regex crate are not affected by this vulnerability.

Overview

The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations already provide sane defaults to prevent attacks. This guarantee is documented and it's considered part of the crate's API.

Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.

Affected versions

All versions of the regex crate before or equal to 1.5.4 are affected by this issue. The fix is include starting from regex 1.5.5.

Mitigations

We recommend everyone accepting user-controlled regexes to upgrade immediately to the latest version of the regex crate.

Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.

Acknowledgements

We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.

We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.

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: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

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.