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.
librespot-playback(28 total, 11 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| alsa | ^0.6 | 0.9.0 | out of date |
| byteorder | ^1.4 | 1.5.0 | up to date |
| cpal | ^0.13 | 0.15.3 | out of date |
| futures-executor | ^0.3 | 0.3.30 | up to date |
| futures-util | ^0.3 | 0.3.30 | up to date |
| glib | ^0.15 | 0.19.6 | out of date |
| gstreamer | ^0.18 | 0.22.4 | out of date |
| gstreamer-app | ^0.18 | 0.22.0 | out of date |
| gstreamer-audio | ^0.18 | 0.22.4 | out of date |
| jack | ^0.10 | 0.11.4 | out of date |
| lewton | ^0.10 | 0.10.2 | up to date |
| libpulse-binding | ^2 | 2.28.1 | up to date |
| libpulse-simple-binding | ^2 | 2.28.1 | up to date |
| librespot-audio | ^0.4.2 | 0.4.2 | up to date |
| librespot-core | ^0.4.2 | 0.4.2 | up to date |
| librespot-metadata | ^0.4.2 | 0.4.2 | up to date |
| log | ^0.4 | 0.4.21 | up to date |
| ogg | ^0.8 | 0.9.1 | out of date |
| parking_lot | ^0.12 | 0.12.2 | up to date |
| portaudio-rs ⚠️ | ^0.3 | 0.3.2 | maybe insecure |
| rand | ^0.8 | 0.8.5 | up to date |
| rand_distr | ^0.4 | 0.4.3 | up to date |
| rodio | ^0.15 | 0.18.0 | out of date |
| sdl2 | ^0.35 | 0.36.0 | out of date |
| shell-words | ^1.0.0 | 1.1.0 | up to date |
| thiserror | ^1 | 1.0.61 | up to date |
| tokio ⚠️ | ^1 | 1.37.0 | maybe insecure |
| zerocopy | ^0.6 | 0.7.34 | out of date |
portaudio-rs: Stream callback function is not unwind safeAffected versions of this crate is not panic safe within callback functions stream_callback and stream_finished_callback.
The call to user-provided closure might panic before a mem::forget call, which then causes a use after free that grants attacker to control the callback function pointer.
This allows an attacker to construct an arbitrary code execution .
The flaw was reported by Phosphorus15.
tokio: reject_remote_clients Configuration corruptionOn 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.
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);