Memory corruption slice-deque

published 2018-12-05 7y ago modified 2026-06-17 4mo ago also GHSA-hr3c-6mmp-6m39 , RUSTSEC-2018-0008 , EUVD-2021-1755

cvss: 9.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.6%; EPSS 1.6% chance of exploitation in 30 days, percentile 76%
public exploits: 0; none known

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.

Patch / fix

fixed in 2

crates.io slice-deque 0.1.16
slice-deque_project slice-deque 0.1.16

Is CVE-2018-20995 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.61% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P
OSV	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
crates.io	slice-deque	<0.1.16 >=0.0.0-0, <0.1.16	0.1.16

Classification

Weakness

CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

rustsec.org /advisories/RUSTSEC-2018-0008.html
web, third-party-advisory, advisory
nvd.nist.gov /vuln/detail/CVE-2018-20995
advisory
github.com /gnzlbg/slice_deque/issues/57
web, report
github.com /gnzlbg/slice_deque
package
crates.io /crates/slice-deque
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.