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 rustmann

Dependencies

(12 total, 9 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 bytes^0.51.6.0out of date
 derive_builder^0.7.00.20.0out of date
 failure^0.10.1.8up to date
 futures-core^0.3.10.3.30up to date
 futures-util^0.3.10.3.30up to date
 getset^0.0.70.1.2out of date
 protobuf^2.103.4.0out of date
 tokio ⚠️^0.21.37.0out of date
 tokio-rustls ⚠️^0.12.00.26.0out of date
 tokio-util^0.20.7.10out of date
 webpki ⚠️^0.210.22.4out of date
 webpki-roots^0.170.26.1out of date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 structopt^0.3.30.3.26up to date
 structopt-derive^0.3.30.4.18out of date

Security Vulnerabilities

tokio-rustls: tokio-rustls reads may cause excessive memory usage

RUSTSEC-2020-0019

tokio-rustls does not call process_new_packets immediately after read, so the expected termination condition wants_read always returns true. As long as new incoming data arrives faster than it is processed and the reader does not return pending, data will be buffered.

This may cause DoS.

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.

webpki: webpki: CPU denial of service in certificate path building

RUSTSEC-2023-0052

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.

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.