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-sdk(14 total, 7 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bincode | ^1.1.2 | 1.3.3 | up to 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.38 | maybe insecure |
| generic-array ⚠️ | ^0.12.0 | 1.0.0 | out of date |
| hex | ^0.3.2 | 0.4.3 | out of date |
| itertools | ^0.8.0 | 0.12.1 | out of date |
| log | ^0.4.2 | 0.4.21 | up to date |
| ring | ^0.13.2 | 0.17.8 | out of date |
| serde | ^1.0.89 | 1.0.198 | up to date |
| serde_derive | ^1.0.89 | 1.0.198 | up to date |
| serde_json | ^1.0.39 | 1.0.116 | up to date |
| sha2 | ^0.8.0 | 0.10.8 | out of date |
| untrusted | ^0.6.2 | 0.9.0 | out of date |
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.