The crate slice-ring-buffer was developed as a fork of slice-deque to continue maintenance and provide security patches, since the latter has been officially unmaintained (RUSTSEC-2020-0158). While slice-ring-buffer has addressed some previously reported memory safety issues inhe...
Product
crates.io slice-deque vulnerabilities
5 published CVES affecting crates.io slice-deque, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 2
- High
- 2
- Medium
- 0
- Low
- 0
- Unscored
- 1
- CISA KEV
- 0
Latest crates.io slice-deque CVEs
Newest publication first
-
HighCVSS 8.1
-
HighCVSS 7.5 EPSS 1.2%
An issue was discovered in the slice-deque crate through 2021-02-19 for Rust. A double drop can occur in SliceDeque::drain_filter upon a panic in a predicate function.
-
Unknown
The author of the slice-deque crate is unresponsive and is not receiving security patches. Maintained alternatives: slice-ring-buffer
-
CriticalCVSS 9.8 EPSS 1.6%
An issue was discovered in the slice-deque crate before 0.1.16 for Rust. move_head_unchecked allows memory corruption because deque updates are mishandled.
-
CriticalCVSS 9.8 EPSS 1.6%
An issue was discovered in the slice-deque crate before 0.2.0 for Rust. There is memory corruption in certain allocation cases.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.