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.
async-fetcher(11 total, 5 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| chrono ⚠️ | ^0.4.6 | 0.4.38 | maybe insecure |
| digest | ^0.8.0 | 0.10.7 | out of date |
| encoding_rs | =0.8.9 | 0.8.34 | out of date |
| failure | ^0.1.3 | 0.1.8 | up to date |
| failure_derive | ^0.1.3 | 0.1.8 | up to date |
| filetime | ^0.2.4 | 0.2.23 | up to date |
| futures | ^0.1.25 | 0.3.30 | out of date |
| hex-view | ^0.1.2 | 0.1.3 | up to date |
| log | ^0.4.6 | 0.4.21 | up to date |
| reqwest | ^0.9.5 | 0.12.4 | out of date |
| tokio ⚠️ | ^0.1.13 | 1.37.0 | out of date |
(5 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix | =0.7.3 | 0.13.3 | out of date |
| actix-web ⚠️ | =0.7.3 | 4.5.1 | out of date |
| flate2 | ^1.0.5 | 1.0.28 | up to date |
| sha2 | ^0.8.0 | 0.10.8 | out of date |
| xz2 | ^0.1.6 | 0.1.7 | up to date |
actix-web: Multiple memory safety issuesAffected versions contain multiple memory safety issues, such as:
Send marker trait to objects that cannot be safely sent between threadsThis may result in a variety of memory corruption scenarios, most likely use-after-free.
A significant refactoring effort has been conducted to resolve these issues.
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
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.