Email me

Rust advisories / slice-deque

Vulnerability CriticalRUSTSEC-2019-0002 · slice-deque

RUSTSEC-2019-0002: Bug in SliceDeque::move_head_unchecked corrupts its memory

Short answerA security vulnerability in the slice-deque crate: Bug in SliceDeque::move_head_unchecked corrupts its memory. Critical severity (CVSS 9.8). Fixed in 0.2.0: update to a fixed version.

Crateslice-deque
TypeVulnerability
Affected versionsBefore 0.2.0.
Fixed in0.2.0
SeverityCritical, CVSS 9.8
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published2019-05-07
Last changed2026-02-04
Also known asCVE-2019-15543, GHSA-c3m3-c39q-pv23

What to do

  1. See which version you have: cargo tree -i slice-deque (it also shows which of your dependencies pulls it in).
  2. Update within your version requirement: cargo update -p slice-deque. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example slice-deque = "0.2.0") or update the dependency that pulls it in.
  3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

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

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.

Other advisories for slice-deque

Full security history of slice-deque

Up next

Same crateslice-deque: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ