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 scylla

Dependencies

(30 total, 14 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arc-swap^1.3.01.7.1up to date
 async-trait^0.1.560.1.89up to date
 base64^0.21.10.22.1out of date
 byteorder^1.3.41.5.0up to date
 bytes^1.0.11.11.0up to date
 chrono^0.4.200.4.42up to date
 dashmap^5.26.1.0out of date
 futures^0.3.60.3.31up to date
 histogram^0.6.90.11.3out of date
 itertools^0.11.00.14.0out of date
 lz4_flex^0.11.10.12.0out of date
 num_enum^0.60.7.5out of date
 openssl ⚠️^0.10.320.10.75maybe insecure
 rand^0.8.30.9.2out of date
 rand_pcg^0.3.10.9.0out of date
 scylla-cql^0.1.01.4.0out of date
 scylla-macros^0.4.01.4.0out of date
 serde^1.01.0.228up to date
 serde_yaml^0.9.140.9.34+deprecatedup to date
 smallvec^1.8.01.15.1up to date
 snap^1.01.1.1up to date
 socket2^0.5.30.6.1out of date
 strum^0.230.27.2out of date
 strum_macros^0.230.27.2out of date
 thiserror^1.02.0.17out of date
 tokio^1.271.48.0up to date
 tokio-openssl^0.6.10.6.5up to date
 tracing^0.1.360.1.44up to date
 url^2.3.12.5.7up to date
 uuid^1.01.19.0up to date

Dev dependencies

(10 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 assert_matches^1.5.01.5.0up to date
 bigdecimal^0.40.4.9up to date
 criterion^0.40.8.1out of date
 ntest^0.9.00.9.5up to date
 num-bigint^0.40.4.6up to date
 rand_chacha^0.3.10.9.0out of date
 scylla-proxy^0.0.30.0.5out of date
 time^0.30.3.44up to date
 tokio^1.271.48.0up to date
 tracing-subscriber ⚠️^0.3.140.3.22maybe insecure

Security Vulnerabilities

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.