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 librespot-connect

Dependencies

(13 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 form_urlencoded^1.01.2.1up to date
 futures-util^0.30.3.31up to date
 librespot-core^0.6.00.6.0up to date
 librespot-playback^0.6.00.6.0up to date
 librespot-protocol^0.6.00.6.0up to date
 log^0.40.4.27up to date
 protobuf ⚠️^3.53.7.2maybe insecure
 rand^0.80.9.1out of date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 thiserror^1.02.0.12out of date
 tokio ⚠️^11.46.1maybe insecure
 tokio-stream^0.10.1.17up 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);

protobuf: Crash due to uncontrolled recursion in protobuf crate

RUSTSEC-2024-0437

Affected version of this crate did not properly parse unknown fields when parsing a user-supplied input.

This allows an attacker to cause a stack overflow when parsing the mssage on untrusted data.