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 spot

Dependencies

(29 total, 14 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 gtk4^0.90.10.0out of date
 libadwaita^0.70.8.0out of date
 gdk4^0.90.10.0out of date
 gio^0.200.21.0out of date
 glib^0.200.21.0out of date
 librespot^0.6.00.6.0up to date
 tokio ⚠️^11.46.1maybe insecure
 futures^0.3.180.3.31up to date
 serde^1.0.1361.0.219up to date
 serde_json^1.0.961.0.140up to date
 isahc^1.7.21.7.2up to date
 rand^0.8.50.9.1out of date
 gettext-rs=0.7.00.7.2out of date
 secret-service^3.0.15.0.0out of date
 gdk-pixbuf^0.200.21.0out of date
 ref_filter_map^1.0.11.0.1up to date
 regex^1.8.31.11.1up to date
 async-std^1.12.01.13.1up to date
 form_urlencoded^1.0.11.2.1up to date
 zbus^3.135.8.0out of date
 zvariant^3.145.6.0out of date
 thiserror^1.0.402.0.12out of date
 lazy_static^1.4.01.5.0up to date
 log^0.4.170.4.27up to date
 env_logger^0.10.00.11.8out of date
 percent-encoding^2.2.02.3.1up to date
 oauth2^4.45.0.0out of date
 url^2.4.12.5.4up to date
 open^5.3.05.3.2up 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);