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-core

Dependencies

(96 total, 18 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 addr^0.15.60.15.6up to date
 affinitypool^0.3.10.3.1up to date
 ahash^0.8.110.8.11up to date
 ammonia^4.0.04.0.0up to date
 arbitrary^1.3.21.4.1up to date
 argon2^0.5.20.5.3up to date
 any_ascii^0.3.20.3.2up to date
 async-channel^2.3.12.3.1up to date
 async-executor^1.13.11.13.1up to date
 async-graphql^7.0.97.0.15up to date
 base64^0.21.50.22.1out of date
 bcrypt^0.15.00.17.0out of date
 bincode^1.3.32.0.0out of date
 blake3^1.5.31.6.1up to date
 bytes^1.5.01.10.1up to date
 castaway^0.2.30.2.3up to date
 cedar-policy^2.4.24.3.3out of date
 chrono^0.4.380.4.40up to date
 ciborium^0.2.10.2.2up to date
 dashmap^5.5.36.1.0out of date
 deunicode^1.4.11.6.0up to date
 dmp^0.2.00.2.0up to date
 ext-sort^0.1.40.1.4up to date
 foundationdb^0.9.00.9.2up to date
 fst^0.4.70.4.7up to date
 futures^0.3.290.3.31up to date
 fuzzy-matcher^0.3.70.3.7up to date
 geo^0.28.00.29.3out of date
 geo-types^0.7.130.7.15up to date
 hex^0.4.30.4.3up to date
 http^1.1.01.2.0up to date
 indxdb^0.6.00.6.0up to date
 ipnet^2.9.02.11.0up to date
 tikv-jemallocator^0.6.00.6.0up to date
 rquickjs^0.8.10.9.0out of date
 jsonwebtoken^9.3.09.3.1up to date
 lexicmp^0.1.00.1.0up to date
 linfa-linalg=0.1.00.2.0out of date
 md-5^0.10.60.10.6up to date
 mimalloc^0.1.430.1.43up to date
 nanoid^0.4.00.4.0up to date
 ndarray=0.15.60.16.1out of date
 ndarray-stats=0.5.10.6.0out of date
 num-traits^0.2.180.2.19up to date
 num_cpus^1.16.01.16.0up to date
 object_store^0.10.20.12.0out of date
 parking_lot^0.12.30.12.3up to date
 pbkdf2^0.12.20.12.2up to date
 pharos^0.5.30.5.3up to date
 phf^0.11.20.11.3up to date
 pin-project-lite^0.2.130.2.16up to date
 quick_cache^0.5.10.6.11out of date
 radix_trie^0.2.10.2.1up to date
 rand^0.8.50.9.0out of date
 rayon^1.10.01.10.0up to date
 reblessive^0.4.20.4.2up to date
 regex^1.10.61.11.1up to date
 regex-syntax^0.8.40.8.5up to date
 reqwest^0.12.70.12.12up to date
 revision^0.110.11.0up to date
 ring ⚠️^0.17.70.17.13maybe insecure
 rmpv^1.0.11.3.0up to date
 roaring^0.10.60.10.10up to date
 rocksdb^0.23.00.23.0up to date
 rust-stemmers^1.2.01.2.0up to date
 rust_decimal^1.36.01.36.0up to date
 scrypt^0.11.00.11.0up to date
 semver^1.0.201.0.26up to date
 serde^1.0.2091.0.219up to date
 serde-content^0.1.00.1.2up to date
 serde_json^1.0.1271.0.140up to date
 sha1^0.10.60.10.6up to date
 sha2^0.10.80.10.8up to date
 snap^1.1.01.1.1up to date
 storekey^0.5.00.5.0up to date
 strsim^0.11.10.11.1up to date
 subtle^2.62.6.1up to date
 surrealcs^0.4.40.4.4up to date
 surrealkv^0.8.10.9.1out of date
 surrealml-core^0.1.10.1.3up to date
 sysinfo^0.33.00.33.1up to date
 tempfile^3.10.13.18.0up to date
 thiserror^1.0.632.0.12out of date
 surrealdb-tikv-client^0.3.0-surreal.1N/Aup to date
 tokio^1.41.11.44.0up to date
 tokio-tungstenite^0.21.00.26.2out of date
 tracing^0.1.400.1.41up to date
 trice^0.4.00.4.0up to date
 ulid^1.1.01.2.0up to date
 unicase^2.7.02.8.1up to date
 url^2.5.02.5.4up to date
 uuid^1.10.01.15.1up to date
 vart^0.8.10.9.2out of 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

(11 total, 2 outdated)

CrateRequiredLatestStatus
 criterion^0.5.10.5.1up to date
 env_logger^0.10.10.11.6out of date
 flate2^1.0.281.1.0up to date
 pprof^0.14.00.14.0up 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.360.3.39up to date
 tokio^1.41.11.44.0up to date
 tracing-subscriber^0.3.180.3.19up to date
 wiremock^0.6.00.6.3up to 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.