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.
solana(31 total, 17 outdated, 5 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| atty | ^0.2 | 0.2.14 | up to date |
| bincode | ^1.0.0 | 2.0.1 | out of date |
| bs58 | ^0.2.0 | 0.5.1 | out of date |
| byteorder | ^1.2.1 | 1.5.0 | up to date |
| chrono ⚠️ | ^0.4.0 | 0.4.41 | maybe insecure |
| clap | ^2.31 | 4.5.40 | out of date |
| dirs | ^1.0.2 | 6.0.0 | out of date |
| env_logger | ^0.5.12 | 0.11.8 | out of date |
| futures | ^0.1.21 | 0.3.31 | out of date |
| generic-array ⚠️ | ^0.11.1 | 1.2.0 | out of date |
| getopts | ^0.2 | 0.2.23 | up to date |
| influx_db_client | ^0.3.4 | 0.6.1 | out of date |
| itertools | ^0.7.8 | 0.14.0 | out of date |
| libc | ^0.2.1 | 0.2.174 | up to date |
| log | ^0.4.2 | 0.4.27 | up to date |
| matches | ^0.1.6 | 0.1.10 | up to date |
| pnet_datalink | ^0.21.0 | 0.35.0 | out of date |
| rand | ^0.5.1 | 0.9.1 | out of date |
| rayon | ^1.0.0 | 1.10.0 | up to date |
| reqwest | ^0.8.6 | 0.12.22 | out of date |
| ring ⚠️ | ^0.13.2 | 0.17.14 | out of date |
| serde | ^1.0.27 | 1.0.219 | up to date |
| serde_derive | ^1.0.27 | 1.0.219 | up to date |
| serde_json | ^1.0.10 | 1.0.140 | up to date |
| sha2 | ^0.7.0 | 0.10.9 | out of date |
| sys-info ⚠️ | ^0.5.6 | 0.9.1 | out of date |
| tokio ⚠️ | ^0.1 | 1.46.1 | out of date |
| tokio-codec | ^0.1 | 0.1.2 | up to date |
| tokio-core | ^0.1.17 | 0.1.18 | up to date |
| tokio-io | ^0.1 | 0.1.13 | up to date |
| untrusted | ^0.6.2 | 0.9.0 | out of date |
(1 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.2 | 0.6.0 | out of date |
sys-info: Double free when calling `sys_info::disk_info` from multiple threadsAffected versions of sys-info use a static, global, list to store temporary disk information while running. The function that cleans up this list,
DFCleanup, assumes a single threaded environment and will try to free the same memory twice in a multithreaded environment.
This results in consistent double-frees and segfaults when calling sys_info::disk_info from multiple threads at once.
The issue was fixed by moving the global variable into a local scope.
generic-array: arr! macro erases lifetimesAffected versions of this crate allowed unsoundly extending
lifetimes using arr! macro. This may result in a variety of
memory corruption scenarios, most likely use-after-free.
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.
ring: Some AES functions may panic when overflow checking is enabled.ring::aead::quic::HeaderProtectionKey::new_mask() may panic when overflow
checking is enabled. In the QUIC protocol, an attacker can induce this panic by
sending a specially-crafted packet. Even unintentionally it is likely to occur
in 1 out of every 2**32 packets sent and/or received.
On 64-bit targets operations using ring::aead::{AES_128_GCM, AES_256_GCM} may
panic when overflow checking is enabled, when encrypting/decrypting approximately
68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols
like TLS and SSH are not affected by this because those protocols break large
amounts of data into small chunks. Similarly, most applications will not
attempt to encrypt/decrypt 64GB of data in one chunk.
Overflow checking is not enabled in release mode by default, but
RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml
profile can override this. Overflow checking is usually enabled by default in
debug mode.