This project contains known security vulnerabilities. Find detailed information at the bottom.
solana(36 total, 20 outdated, 2 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bincode | ^1.0.0 | 3.0.0 | out of date |
| bs58 | ^0.2.0 | 0.5.1 | out of date |
| bv | ^0.10.0 | 0.11.1 | out of date |
| byteorder | ^1.2.1 | 1.5.0 | up to date |
| chrono | ^0.4.0 | 0.4.45 | up to date |
| hashbrown | ^0.1.7 | 0.17.1 | out of date |
| indexmap | ^1.0 | 2.14.2 | out of date |
| itertools | ^0.8.0 | 0.15.0 | out of date |
| libc | ^0.2.45 | 0.2.191 | up to date |
| log | ^0.4.2 | 0.4.35 | up to date |
| nix | ^0.12.0 | 0.31.3 | out of date |
| rand | ^0.6.1 | 0.10.3 | out of date |
| rand_chacha | ^0.1.0 | 0.10.0 | out of date |
| rayon | ^1.0.0 | 1.12.0 | up to date |
| reqwest | ^0.9.0 | 0.13.5 | out of date |
| ring ⚠️ | ^0.13.2 | 0.17.14 | insecure |
| rocksdb ⚠️ | ^0.10.1 | 0.25.0 | insecure |
| serde | ^1.0.82 | 1.0.229 | up to date |
| serde_derive | ^1.0.82 | 1.0.229 | up to date |
| serde_json | ^1.0.10 | 1.0.154 | up to date |
| solana-bpfloader | ^0.11.0 | 0.15.3 | out of date |
| solana-drone | ^0.11.0 | N/A | up to date |
| solana-jsonrpc-core | ^0.4.0 | N/A | up to date |
| solana-jsonrpc-http-server | ^0.4.0 | N/A | up to date |
| solana-jsonrpc-macros | ^0.4.0 | N/A | up to date |
| solana-jsonrpc-pubsub | ^0.4.0 | N/A | up to date |
| solana-jsonrpc-ws-server | ^0.4.0 | N/A | up to date |
| solana-logger | ^0.11.0 | 3.0.0 | out of date |
| solana-metrics | ^0.11.0 | 4.4.0 | out of date |
| solana-native-loader | ^0.11.0 | 0.11.0 | up to date |
| solana-netutil | ^0.11.0 | 0.20.5 | out of date |
| solana-sdk | ^0.11.0 | 5.0.0 | out of date |
| solana-system-program | ^0.11.0 | 4.4.0 | out of date |
| tokio | ^0.1 | 1.54.1 | out of date |
| tokio-codec | ^0.1 | 0.1.2 | up to date |
| untrusted | ^0.6.2 | 0.9.0 | out of date |
(2 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| hex-literal | ^0.1.1 | 1.1.0 | out of date |
| matches | ^0.1.6 | 0.1.10 | up to date |
rocksdb: Out-of-bounds read when opening multiple column families with TTLAffected versions of this crate called the RocksDB C API
rocksdb_open_column_families_with_ttl() with a pointer to a single integer
TTL value, but one TTL value for each column family is expected.
This is only relevant when using
rocksdb::DBWithThreadMode::open_cf_descriptors_with_ttl() with multiple
column families.
This bug has been fixed in v0.19.0.
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.