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

Crate libsbc

Dependencies

(3 total, 1 outdated, 1 insecure)

CrateRequiredLatestStatus
 failure^0.1.20.1.8up to date
 libsbc-sys^0.1.10.1.2up to date
 slice-deque ⚠️^0.1.130.3.0insecure

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 alsa^0.2.00.9.0out of date
 byteorder^11.5.0up to date

Security Vulnerabilities

slice-deque: Bug in SliceDeque::move_head_unchecked corrupts its memory

RUSTSEC-2019-0002

Affected versions of this crate entered a corrupted state if mem::size_of::<T>() % allocation_granularity() != 0 and a specific allocation pattern was used: sufficiently shifting the deque elements over the mirrored page boundary.

This allows an attacker that controls controls both element insertion and removal to corrupt the deque, such that reading elements from it would read bytes corresponding to other elements in the deque. (e.g. a read of T could read some bytes from one value and some bytes from an adjacent one, resulting in a T whose value representation is not meaningful). This is undefined behavior.

The flaw was corrected by using a pair of pointers to track the head and tail of the deque instead of a pair of indices. This pair of pointers are represented using a Rust slice.

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.