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.
tokio-imap(7 total, 6 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes | ^0.4 | 1.6.0 | out of date |
| futures-preview | ^0.3.0-alpha.19 | 0.2.2 | up to date |
| imap-proto | ^0.9.1 | 0.16.4 | out of date |
| nom | ^5 | 7.1.3 | out of date |
| tokio ⚠️ | ^0.2.0-alpha.6 | 1.37.0 | out of date |
| tokio-rustls ⚠️ | ^0.12.0-alpha.4 | 0.26.0 | out of date |
| webpki-roots | ^0.18.0 | 0.26.1 | out of date |
tokio-rustls: tokio-rustls reads may cause excessive memory usagetokio-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` channelIf 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.