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 taliyah

Dependencies

(15 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aspotify^0.7.10.7.1up to date
 chrono^0.4.220.4.38up to date
 git2^0.15.00.18.3out of date
 humantime^2.1.02.1.0up to date
 itertools^0.10.50.13.0out of date
 lastfm-rs^0.5.00.5.0up to date
 reqwest^0.11.120.12.4out of date
 serde^1.0.1471.0.202up to date
 serde_json^1.0.871.0.117up to date
 tokio ⚠️^1.21.21.37.0maybe insecure
 toml^0.5.90.8.13out of date
 tracing^0.1.370.1.40up to date
 tracing-futures^0.2.50.2.5up to date
 tracing-log^0.1.30.2.0out of date
 tracing-subscriber^0.3.160.3.18up 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);