~ / search / GHSA-c3m3-c39q-pv23

GHSA-c3m3-c39q-pv23

Out of bounds write in slice-deque

Source: GitHub Advisory Database (reviewed) Critical CVE-2019-15543

Packages

EcosystemPackageAffectedFixed in
crates.io slice-deque < 0.2.0 0.2.0

Details

As written in the advisory (Markdown source, shown as plain text).

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.

References

External links from the advisory. They lead to third-party sites.