futures-rustls 0.24.0

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 `futures-rustls`

Dependencies

(2 total, 1 outdated, 1 possibly insecure)

Crate	Required	Latest	Status
futures-io	`^0.3`	`0.3.31`	up to date
rustls ⚠️	`^0.21`	`0.23.16`	out of date

Dev dependencies

(6 total, 4 outdated, 1 possibly insecure)

Crate	Required	Latest	Status
futures-util	`^0.3.1`	`0.3.31`	up to date
lazy_static	`^1`	`1.5.0`	up to date
rustls-pemfile	`^1`	`2.2.0`	out of date
smol	`^1`	`2.0.2`	out of date
rustls-webpki ⚠️	`^0.100`	`0.102.8`	out of date
webpki-roots	`^0.23`	`0.26.6`	out of date

Security Vulnerabilities

`rustls-webpki`: rustls-webpki: CPU denial of service in certificate path building

RUSTSEC-2023-0053

When 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.

We now give each path building operation a budget of 100 signature verifications.

The original webpki crate is also affected.

This was previously reported in the original crate https://github.com/briansmith/webpki/issues/69 and re-reported to us recently by Luke Malinowski.

`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.