Deps.rs

surrealdb 1.5.6

[![dependency status](https://deps.rs/crate/surrealdb/1.5.6/status.svg)](https://deps.rs/crate/surrealdb/1.5.6)

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.

Crate surrealdb

Dependencies

(33 total, 10 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bincode^1.3.32.0.1out of date
 async-channel^1.9.02.3.1out of date
 chrono^0.4.310.4.40up to date
 dmp^0.2.00.2.3up to date
 flume^0.11.00.11.1up to date
 futures^0.3.290.3.31up to date
 futures-concurrency^7.4.37.6.3up to date
 geo^0.27.00.30.0out of date
 indexmap^2.1.02.9.0up to date
 native-tls^0.2.110.2.14up to date
 once_cell^1.18.01.21.3up to date
 path-clean^1.0.11.0.1up to date
 pharos^0.5.30.5.3up to date
 reqwest^0.11.220.12.15out of date
 revision^0.7.00.11.0out of date
 ring ⚠️^0.17.70.17.14maybe insecure
 rust_decimal^1.33.11.37.1up to date
 rustls^0.21.110.23.26out of date
 semver^1.0.201.0.26up to date
 serde^1.0.1931.0.219up to date
 serde_json^1.0.1081.0.140up to date
 surrealdb-core=2.0.0-1.5.62.2.2out of date
 thiserror^1.0.502.0.12out of date
 tokio^1.34.01.44.2up to date
 tokio-tungstenite^0.20.10.26.2out of date
 tokio-util^0.7.100.7.14up to date
 tracing^0.1.400.1.41up to date
 trice^0.4.00.4.0up to date
 url^2.5.02.5.4up to date
 uuid^1.6.11.16.0up to date
 wasm-bindgen-futures^0.4.390.4.50up to date
 wasmtimer^0.2.00.4.1out of date
 ws_stream_wasm^0.7.40.7.4up to date

Dev dependencies

(16 total, 6 outdated)

CrateRequiredLatestStatus
 criterion^0.5.10.5.1up to date
 env_logger^0.10.10.11.8out of date
 flate2^1.0.281.1.1up to date
 hashbrown^0.14.50.15.2out of date
 pprof^0.13.00.14.0out of date
 radix_trie^0.2.10.2.1up to date
 rand^0.8.50.9.1out of date
 regex^1.10.21.11.1up to date
 serial_test^2.0.03.2.0out of date
 temp-dir^0.1.110.1.14up to date
 test-log^0.2.130.2.17up to date
 time^0.3.300.3.41up to date
 tokio^1.34.01.44.2up to date
 tracing-subscriber^0.3.180.3.19up to date
 ulid^1.1.01.2.1up to date
 wiremock^0.5.220.6.3out of date

Security Vulnerabilities

ring: Some AES functions may panic when overflow checking is enabled.

RUSTSEC-2025-0009

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.