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 crusty

Dependencies

(30 total, 18 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.141.48.0maybe insecure
 itertools~0.10.10.14.0out of date
 strum^0.230.27.2out of date
 anyhow~1.0.401.0.100up to date
 futures~0.3.140.3.31up to date
 tracing~0.1.250.1.43up to date
 tracing-subscriber ⚠️~0.3.00.3.22maybe insecure
 tracing-futures~0.2.50.2.5up to date
 config~0.11.00.15.19out of date
 ipnetwork~0.18.00.21.1out of date
 crusty-core^0.820.82.0up to date
 tracing-tools~0.5.00.6.0out of date
 clickhouse~0.9.10.14.1out of date
 redis~0.21.00.32.7out of date
 serde_json^1.01.0.145up to date
 serde~1.0.1251.0.228up to date
 http~0.2.31.4.0out of date
 cache_2q~0.10.10.10.1up to date
 crc32fast~1.2.11.5.0out of date
 bytes~1.1.01.11.0out of date
 backoff~0.3.00.4.0out of date
 num_cpus~1.13.01.17.0out of date
 url~2.2.12.5.7out of date
 once_cell~1.8.01.21.3out of date
 fdlimit~0.2.10.3.0out of date
 humanize-rs~0.10.1.5up to date
 relabuf~0.16.00.16.0up to date
 base64~0.13.00.22.1out of date
 html5ever~0.25.10.36.1out of date
 lol_html~0.3.02.7.0out of date

Build dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 vergen~59.0.6out of date
 anyhow~1.0.401.0.100up to date

Crate interop

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 serde~1.0.1251.0.228up to date

Crate redis-utils

Dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 redis-module~0.24.02.0.7out of date

Crate redis-queue

Dependencies

(6 total, 3 outdated)

CrateRequiredLatestStatus
 anyhow~1.0.401.0.100up to date
 thiserror~1.0.242.0.17out of date
 serde~1.0.1251.0.228up to date
 serde_json^1.01.0.145up to date
 redis-module~0.24.02.0.7out of date
 validator~0.14.00.20.0out of date

Crate redis-calc

Dependencies

(7 total, 4 outdated)

CrateRequiredLatestStatus
 anyhow~1.0.401.0.100up to date
 thiserror~1.0.242.0.17out of date
 serde~1.0.1251.0.228up to date
 serde_json^1.01.0.145up to date
 redis-module~0.24.02.0.7out of date
 validator~0.14.00.20.0out of date
 itertools~0.10.10.14.0out of date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

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.