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 spotify-tui

Dependencies

(15 total, 8 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.261.0.82up to date
 backtrace^0.3.460.3.71up to date
 clap^2.33.04.5.4out of date
 clipboard^0.5.00.5.0up to date
 crossterm^0.170.27.0out of date
 dirs^2.0.25.0.1out of date
 proc-macro2^1.0.91.0.81up to date
 rand^0.7.30.8.5out of date
 rspotify^0.9.00.13.1out of date
 serde^1.01.0.198up to date
 serde_json^1.01.0.116up to date
 serde_yaml ⚠️^0.80.9.34+deprecatedout of date
 tokio ⚠️^0.21.37.0out of date
 tui^0.8.00.19.0out of date
 unicode-width^0.1.70.1.11up to date

Security Vulnerabilities

serde_yaml: Uncontrolled recursion leads to abort in deserialization

RUSTSEC-2018-0005

Affected versions of this crate did not properly check for recursion while deserializing aliases.

This allows an attacker to make a YAML file with an alias referring to itself causing an abort.

The flaw was corrected by checking the recursion depth.

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If 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.