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.
ncspot(29 total, 20 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| chrono ⚠️ | ^0.4 | 0.4.45 | maybe insecure |
| clap | ^2.33.0 | 4.6.6 | out of date |
| clipboard | ^0.5 | 0.5.0 | up to date |
| crossbeam-channel | ^0.4 | 0.5.17 | out of date |
| cursive | ^0.14 | 0.21.1 | out of date |
| dbus | ^0.6.4 | 0.9.12 | out of date |
| directories | ^2.0 | 6.0.0 | out of date |
| failure | ^0.1 | 0.1.8 | up to date |
| fern | ^0.5 | 0.7.1 | out of date |
| futures | ^0.1 | 0.3.34 | out of date |
| lazy_static | ^1.3.0 | 1.5.0 | up to date |
| librespot-core | ^0.1.1 | 0.8.0 | out of date |
| librespot-playback | ^0.1.1 | 0.8.0 | out of date |
| librespot-protocol | ^0.1.1 | 0.8.0 | out of date |
| log | ^0.4.0 | 0.4.34 | up to date |
| rand | ^0.7 | 0.10.2 | out of date |
| reqwest | ^0.9 | 0.13.5 | out of date |
| rspotify | ^0.8 | 0.16.1 | out of date |
| serde | ^1.0 | 1.0.229 | up to date |
| serde_json | ^1.0 | 1.0.151 | up to date |
| strum | ^0.17.1 | 0.28.0 | out of date |
| strum_macros | ^0.17.1 | 0.28.0 | out of date |
| tokio ⚠️ | ^0.1 | 1.53.1 | out of date |
| tokio-core | ^0.1 | 0.1.18 | up to date |
| tokio-timer | ^0.2 | 0.2.13 | up to date |
| toml | ^0.5 | 1.1.6+spec-1.1.0 | out of date |
| unicode-width | ^0.1.5 | 0.2.2 | out of date |
| url | ^1.7 | 2.5.8 | out of date |
| webbrowser ⚠️ | ^0.5 | 1.2.4 | out of date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
tokio: Data race when sending and receiving after closing a `oneshot` channelIf a tokio::sync::oneshot channel is closed (via the
oneshot::Receiver::close method), a data race may occur if the
oneshot::Sender::send method is called while the corresponding
oneshot::Receiver is awaited or calling try_recv.
When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.
Note that the race only occurs when both halves of the channel are used
after the Receiver half has called close. Code where close is not used, or where the
Receiver is not awaited and try_recv is not called after calling close,
is not affected.
See tokio#4225 for more details.
webbrowser: Unix `BROWSER` handling allows browser argument injectionOn Unix platforms handled by src/unix.rs, affected versions substitute the
caller-supplied URL into the BROWSER environment-variable template before
tokenizing the resulting string with split_ascii_whitespace(). If an
application passes an attacker-controlled non-HTTP(S) URL whose parsed form
retains spaces and the effective BROWSER template contains %s, text that
should remain within one URL argument becomes additional browser arguments.
The issue was reproduced with Chromium by injecting
--remote-debugging-port, which exposed a local DevTools endpoint, and
--proxy-server, which redirected browser traffic through an
attacker-controlled proxy. The available arguments and resulting impact depend
on the browser launched by the affected application.
Version 1.2.2 fixes the issue by tokenizing the BROWSER template before
substituting the URL, preserving the URL as part of a single argument. Users
should upgrade to version 1.2.2 or later. Applications that only need HTTP(S)
URLs can also enable the crate's hardened feature as defense in depth.
This issue was reported by @dywzju09-blip.