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

Dependencies

(27 total, 18 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.141.48.0maybe insecure
 strum~0.240.27.2out of date
 tracing-tools~0.5.00.6.0out of date
 flume~0.10.50.11.1out of date
 futures-lite~1.12.02.6.1out of date
 serde~1.0.1251.0.228up to date
 hyper~0.14.121.8.1out of date
 robotstxt-with-cache~0.4.00.4.0up to date
 trust-dns-resolver~0.22.00.23.2out of date
 hyper-tls~0.5.00.6.0out of date
 url~2.3.12.5.7out of date
 http~0.2.31.4.0out of date
 bytes~1.3.01.11.0out of date
 flate2~1.0.201.1.7out of date
 select~0.6.00.6.1up to date
 ipnet~2.7.02.11.0out of date
 humansize~2.1.32.1.3up to date
 humanize-rs~0.1.50.1.5up to date
 tracing~0.1.250.1.43up to date
 thiserror~1.0.242.0.17out of date
 anyhow~1.0.401.0.100up to date
 pin-project~1.0.71.1.10out of date
 lazy_static~1.4.01.5.0out of date
 num_cpus~1.15.01.17.0out of date
 rand~0.8.00.9.2out of date
 derivative~2.2.02.2.0up to date
 core_affinity~0.7.60.8.3out of date

Dev dependencies

(4 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 html5ever~0.26.00.36.1out of date
 markup5ever~0.11.00.36.1out of date
 tracing-subscriber ⚠️~0.3.20.3.22maybe insecure
 tracing~0.1.250.1.43up to 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.