● crates.io crate
slice-deque
Slice-deque has five security advisories. The newest release any of them names as its own fix is 0.2.0, though an advisory still lists that release as affected.
As of , slice-deque has five security advisories. The newest release any of them names as its own fix is 0.2.0, though an advisory still lists that release as affected.
Your version, and the version to upgrade to
| If you run | Upgrade to | Advisories |
|---|---|---|
| All versions | None in this row; 2 of its 5 advisories name a fixed version | 5 advisories |
No row names a version to upgrade to, because an advisory lists the newer releases as affected and names no fix for them. 2 of the 5 advisories name a fixed version that this page reads; the list of advisories below gives them.
Security advisories, newest first
RustSec also lists notices that a crate is unmaintained. The records this page reads do not tell them apart from the other advisories, so an advisory with no fixed version may be one.
| Advisory | What it is | Affects | Fixed in | Published |
|---|---|---|---|---|
| GHSA-7mcq-f592-pf7vRUSTSEC-2025-0044 | Slice Ring Buffer and Slice Deque contains four unique double-free vulnerabilities triggered through safe APIsHigh severity | Up to and including 0.3.0 | No fixed version listed | |
| CVE-2021-29938GHSA-p9gf-gmfv-398m, RUSTSEC-2021-0047 | Double free in slice-dequeHigh severity | All versions | No fixed version listed | |
| RUSTSEC-2020-0158 | slice-deque is unmaintained | All versions | No fixed version listed | |
| CVE-2019-15543GHSA-c3m3-c39q-pv23, RUSTSEC-2019-0002 | Out of bounds write in slice-dequeCritical severity | Before 0.2.0 | 0.2.0 | |
| CVE-2018-20995GHSA-hr3c-6mmp-6m39, RUSTSEC-2018-0008 | Memory corruption slice-dequeCritical severity | Before 0.1.16 | 0.1.16 |
Sources
- Package advisories from the GitHub Advisory Database (CC BY 4.0). Version ranges are reworded as sentences (source). Licence: CC BY 4.0