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.
rustls(12 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| aws-lc-rs | ^1.12 | 1.12.6 | up to date |
| brotli | ^7 | 7.0.0 | up to date |
| brotli-decompressor | ^4.0.1 | 4.0.2 | up to date |
| hashbrown ⚠️ | ^0.15 | 0.15.2 | maybe insecure |
| log | ^0.4.8 | 0.4.26 | up to date |
| once_cell | ^1.16 | 1.21.1 | up to date |
| rustls-pki-types | ^1.11 | 1.11.0 | up to date |
| ring ⚠️ | ^0.17 | 0.17.14 | maybe insecure |
| subtle | ^2.5.0 | 2.6.1 | up to date |
| rustls-webpki | ^0.103 | 0.103.0 | up to date |
| zeroize | ^1.7 | 1.8.1 | up to date |
| zlib-rs | ^0.4 | 0.4.2 | up to date |
(13 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22 | 0.22.1 | up to date |
| bencher | ^0.1.5 | 0.1.5 | up to date |
| env_logger | ^0.11 | 0.11.7 | up to date |
| hex | ^0.4 | 0.4.3 | up to date |
| log | ^0.4.8 | 0.4.26 | up to date |
| macro_rules_attribute | ^0.2 | 0.2.0 | up to date |
| num-bigint | ^0.4.4 | 0.4.6 | up to date |
| rcgen | ^0.13 | 0.13.2 | up to date |
| serde | ^1 | 1.0.219 | up to date |
| serde_json | ^1 | 1.0.140 | up to date |
| time | ^0.3.6 | 0.3.40 | up to date |
| webpki-roots | ^0.26 | 0.26.8 | up to date |
| x509-parser | ^0.17 | 0.17.0 | up to date |
hashbrown: Borsh serialization of HashMap is non-canonicalThe borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding.
This can result in consensus splits and cause equivalent objects to be considered distinct.
This was patched in 0.15.1.
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.