This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate minimp3

Dependencies

(4 total, 1 insecure, 1 possibly insecure)

CrateRequiredLatestStatus
 minimp3-sys^0.30.3.2up to date
 slice-deque ⚠️^0.3.00.3.0insecure
 thiserror^1.0.231.0.31up to date
 tokio ⚠️^1.01.18.2maybe insecure

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.3.80.3.21up to date
 tokio ⚠️^1.01.18.2maybe insecure

Security Vulnerabilities

slice-deque: SliceDeque::drain_filter can double drop an element if the predicate panics

RUSTSEC-2021-0047

Affected versions of the crate incremented the current index of the drain filter iterator before calling the predicate function self.pred.

If the predicate function panics, it is possible for the last element in the iterator to be dropped twice.

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.